Develop Bugs

[kernel] Root Stock Kernel

Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
Froyo only
Strock "root" Kernel -
boot.img only
http://dl.dropbox.com/u/8699733/inc2/boot.img
CWR Flashable with wifi module
http://dl.dropbox.com/u/8699733/inc2/inc2_stock_kernel_.zip
NOTE I will not be maintaining this thread

Amazingly fast work... part of me wonders how fast MIUI can get organized for this... that would be worth it all.

drtchocky said:
Amazingly fast work... part of me wonders how fast MIUI can get organized for this... that would be worth it all.
Click to expand...
Click to collapse
its 3 small changes, took 2 minutes max

Could u give a short intros for it?

Relay said:
Could u give a short intros for it?
Click to expand...
Click to collapse
its a stock kernel with presistant adb, and ""root"" adb

jcase said:
its a stock kernel with presistant adb, and ""root"" adb
Click to expand...
Click to collapse
LOL
niiiice

My kernel is ver 2.6.35.10-g20416a6, is it older than yours?

jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
I don't wanna sound like a noob here, I know how to use CWR, but in reference to fastboot, thats not the fastboot that makes the phone boot faster. But fastboot used in adb for back ups right?? Not asking for a description i just went through the entire life of my dinc 1 and thought I knew everything and never heard of fastboot. Wanna make sure I understand and read up on the right thing...
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse

scumfromohio said:
jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
I don't wanna sound like a noob here, I know how to use CWR, but in reference to fastboot, thats not the fastboot that makes the phone boot faster. But fastboot used in adb for back ups right?? Not asking for a description i just went through the entire life of my dinc 1 and thought I knew everything and never heard of fastboot. Wanna make sure I understand and read up on the right thing...
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
fastboot as in fastboot commands.
Click to expand...
Click to collapse

Relay said:
My kernel is ver 2.6.35.10-g20416a6, is it older than yours?
Click to expand...
Click to collapse
Mine is 2.6.35.9

Relay said:
My kernel is ver 2.6.35.10-g20416a6, is it older than yours?
Click to expand...
Click to collapse
seems newever, and your software is much different than ours, is that an inc2 or S, or is it running on GSM or something?

HELP!!
I tried to flash the overclocked kernel and now Im stuck in a bootloop and can't load recovery or be recognized in fastboot usb. It seems like I may have bricked my phone any suggestions. PLEASE HELP
update - I fixed it lol almost thought my dinc 2 was a brick

I may be in the same situation and would like to know how you solved your problem.
I rooted successfully and was running the Gingersense rom with the stock kernel. I wanted to OC a kernel so I downloaded one that I think was intended to run with MIUI. I made a backup so I figured if the kernel didn't work I could always go back.
After installing the new kernel I went into a boot loop. I pulled the battery, got into recovery and tried to restore a backup, but now I freeze on the HTC screen. I've tried three different backups and none of them work -- all freeze on the HTC screen.
I am becoming desperate. Any help would be greatly appreciated.

Have you tried wiping everything (including /system under "mounts and storage") before restoring the backup? Or tried flashing a different rom? Probably happened because the kernels for AOSP roms and sense roms aren't interchangeable. I would think that restoring a backup would rewrite the boot partition though, which should fix it..

I wiped everything (did data wipe/factory resets as well as wiping everything individually, several times) and could never get any of my backups to work.
I finally copied CM7.1 beta onto the SD card and flashed that (after first having to scrounge to find a card reader and computer that would read an SDHC card) and that worked.
I tried restoring one of my previous backups over CM7.1 (with and without wiping) and went back to freezing on the HTC screen again on each one of them. Don't understand that, since everything was working fine when those backups were made.
Anyway, now I'm using CM7.1 and have a working phone again.

Thanks for your work on this. Much appreciated for helping to realize my dream of a fully-rooted Inc2.
/bow

Ihave the same issues with backup not restoring and getting the white screen. Might need a new SD card.
Sent from my ADR6350 using XDA App

jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
Froyo only
Strock "root" Kernel -
boot.img only
http://dl.dropbox.com/u/8699733/inc2/boot.img
CWR Flashable with wifi module
http://dl.dropbox.com/u/8699733/inc2/inc2_stock_kernel_.zip
NOTE I will not be maintaining this thread
Click to expand...
Click to collapse
links dont work

dgm_mixtoon said:
links dont work
Click to expand...
Click to collapse
links 4years old

Major problems! Phone completely bricked nothing is fixing! Please help

I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.

Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2

jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME

May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2

dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide

The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536

If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.

sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation

CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.

sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.

sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.

CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance

If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully

CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.

dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.

Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this

flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.

I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app

TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.

Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium

HELP! Cyanogenmod Broke My Kindle Fire!

Hello all,
Right now I am getting very pissed at my kindle. I rooted it with KFU and installed TWRP and then flashed it to twa_priv's CM10.1/SGT7 ROM. After flashing it and gApps it got stuck on the cyanogen boot screen/animation. I tried to reboot it but it doesn't even show the option to go into TWRP anymore. It shows the orange Kindle Fire logo then goes straight to cyanogen and the logo just keeps spinning. I am getting ADB status when I connect it to KFU but I can not do anything with it or put it into Fastboot. Any help would be greatly appreciated at this point!

Seriously no help?

stergmtl said:
Seriously no help?
Click to expand...
Click to collapse
Patience grasshopper
stergmtl said:
Right now I am getting very pissed at my kindle. I rooted it with KFU and installed TWRP and then flashed it to twa_priv's CM10.1/SGT7 ROM. After flashing it and gApps it got stuck on the cyanogen boot screen/animation. I tried to reboot it but it doesn't even show the option to go into TWRP anymore. It shows the orange Kindle Fire logo then goes straight to cyanogen and the logo just keeps spinning. I am getting ADB status when I connect it to KFU but I can not do anything with it or put it into Fastboot. Any help would be greatly appreciated at this point!
Click to expand...
Click to collapse
You shouldn't be mad at the Kindle, it didn't do anything wrong.
On the other hand, you probably failed to wipe system and factory reset before flashing the ROM (installation instructions are in twa_priv's SGT7 thread btw). Unfortunately, short of opening the case and list of other things that are outside the scope of this conversation, you're going to need a factory cable to get into fastboot.
Sent from my KFHD 8.9 using Tapatalk 2

Discourse wtorjt
soupmagnet said:
Patience grasshopper
You shouldn't be mad at the Kindle, it didn't do anything wrong.
On the other hand, you probably failed to wipe system and factory reset before flashing the ROM (installation instructions are in twa_priv's SGT7 thread btw). Unfortunately, short of opening the case and list of other things that are outside the scope of this conversation, you're going to need a factory cable to get into fastboot.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
I have the wall charger if that's what you mean by factory cable. Any more instructions you can give me so I can get back into TWRP?

If you're getting adb and the Kfu works why cant you just change to fadtboot from there?or re install root from here, adb should be able to give command line to access twrp
Sent from my Kindle Fire using xda app-developers app

Vintage144 said:
If you're getting adb and the Kfu works why cant you just change to fadtboot from there?or re install root from here, adb should be able to give command line to access twrp
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Because you need the shell to do so.
stergmtl said:
I have the wall charger if that's what you mean by factory cable. Any more instructions you can give me so I can get back into TWRP?
Click to expand...
Click to collapse
No, the factory cable is different. Look in the KF General forum for more information.
Sent from my KFHD 8.9 using Tapatalk 2

soupmagnet said:
Because you need the shell to do so.
No, the factory cable is different. Look in the KF General forum for more information.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
Would you recommend buying one on ebay from china?

stergmtl said:
Would you recommend buying one on ebay from china?
Click to expand...
Click to collapse
Personally I would say go with Skorpn's. They are made in small batches with great quality, fairly inexpensive, fast shipping, and everyone who gets theirs from him seem quite pleased with it overall. He's got a pretty good reputation on XDA so you should probably look into it, if not for that reason alone.
Sent from my KFHD 8.9 using Tapatalk 2

Unlocked Bootloader for 10.3

Will there eventually be an app for unlocking the bootloader on the 10.3 firmware? I don't have the factory cable and it sounds like a lot of people have bricked their device doing the downgrade to 10.2.

I hope so. I am not gonna even try it... Lol instead rooted it and used Kindlefree app to install Nova and used titanium backup. So it's "like" Android but not quite lol....
Sent from my Nexus 4 using xda app-developers app

It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD

I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.

flopower1996 said:
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
But if I downgrade my bootloader I won't have to use the whole 2nd bootloader method and all that right? Won't I then just be able to use some utility to flash TWRP and then flash a ROM? This Kindle thing is probably a little more intimidating than anything else I've messed with. I have mine rooted and a bunch of other hacks but I want pure Android on. I don't want a brick though..
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:58 PM ---------- Previous post was at 01:58 PM ----------
jwort93 said:
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
Click to expand...
Click to collapse
Which utility did you use and did you need a fastboot cable?
Sent from my Nexus 4 using xda app-developers app

You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app

jcnbama said:
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD

flopower1996 said:
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app

jcnbama said:
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD

flopower1996 said:
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?

jcnbama said:
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
Click to expand...
Click to collapse
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD

flopower1996 said:
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:

jcnbama said:
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
Click to expand...
Click to collapse
You have fastboot cable?
--
Sent from my mind to your screen.

mindmajick said:
You have fastboot cable?
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app

jcnbama said:
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.

mindmajick said:
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I actually tried the side load through TWRP. When I typed "adb devices" it showed my device in host mode and the file wouldn't transfer although TWRP was in adb sideload mode. But then I just thought "oh well guess I'll restore my backup" lol. Yeah that didn't work out..
Sent you a P. M. BTW. thanks again!
Sent from my Nexus 4 using xda app-developers app

Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!

punkcitykid said:
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
Click to expand...
Click to collapse
**As a special note however DO NOT restore your factory backup if you have trouble. You will end up like me. Bootlooping with a fast boot cable in the mail.** if I could go back in time I would've downloaded the files via a hard line rather than slow wifi and maybe even double downloaded.. Oh well. This is a learning opportunity.
Sent from my Nexus 4 using xda app-developers app

[Q] How to revert to STOCK ROM but touch screen nonfunctional!

I have fastboot, ADB, and TWRP installed but I can't flash the stock rom through TWRP because my touch screen won't respond to touch, I'm just trying to send it back to Amazon with factory settings, any ideas? And I do have a factory cable.
Thank You!
~carlybelle

carlybelle said:
I have fastboot, ADB, and TWRP installed but I can't flash the stock rom through TWRP because my touch screen won't respond to touch, I'm just trying to send it back to Amazon with factory settings, any ideas? And I do have a factory cable.
Thank You!
~carlybelle
Click to expand...
Click to collapse
Did you ever install a theme for TWRP, or has this been an ongoing issue for the whole device?

soupmagnet said:
Did you ever install a theme for TWRP, or has this been an ongoing issue for the whole device?
Click to expand...
Click to collapse
This has been an ongoing issue for the whole device, if I hard reset, it will work 1% of the time.

carlybelle said:
This has been an ongoing issue for the whole device, if I hard reset, it will work 1% of the time.
Click to expand...
Click to collapse
You may want to open it up and make sure the digitizer cable isn't loose or disconnected.

Wouldn't it be easier to Factory Reset through KFU or ADB?
Sent from my Amazon Kindle Fire using xda app-developers app

404-Not Found said:
Wouldn't it be easier to Factory Reset through KFU or ADB?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That'd be a neat little trick considering you can't factory reset with ADB (at least not that I've seen). You can wipe cache and data with fastboot, but that doesn't really do anything about the touchscreen problem or the fact that the OP wants to install the stock ROM so it can be sent back for replacement.
With that being said, if someone around here is kind enough, OP, you may be able to get a saved stock system.img to flash in fastboot along with stock versions of the bootloader and recovery. After which, a few simple ADB commands will remove superuser.apk and 'su' so it can be sent back for replacement, if you can't resolve the problem on your own.

soupmagnet said:
That'd be a neat little trick considering you can't factory reset with ADB (at least not that I've seen). You can wipe cache and data with fastboot, but that doesn't really do anything about the touchscreen problem or the fact that the OP wants to install the stock ROM so it can be sent back for replacement.
With that being said, if someone around here is kind enough, OP, you may be able to get a saved stock system.img to flash in fastboot along with stock versions of the bootloader and recovery. After which, a few simple ADB commands will remove superuser.apk and 'su' so it can be sent back for replacement, if you can't resolve the problem on your own.
Click to expand...
Click to collapse
There was a option to flash a stock.zip in kfu
Sent from my Amazon Kindle Fire using xda app-developers app