Related
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
chrisms1973 said:
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
Click to expand...
Click to collapse
You could try using ACMEUninstaller, but I'm not 100% certain what will happen.
Check here: http://forum.xda-developers.com/showthread.php?p=20989526
One other thing... I can't turn it off. I keep it charged for Netflix, so I havent had it die yet.
Sent from my Galaxy Nexus using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2176848
[VIDEO] Idiot's Guide - How to Install CM10 on the HP Touchpad
Check here also . Eventually you will need to put the tp into webos recovery ( black screen with USB symbol)
chrisms1973 said:
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
Click to expand...
Click to collapse
Make sure your TP is chargerd and reboot it using the power and home key button. Once you do that hold down the volume up key and while it plugged into the PC. That will get you into WebOS Recovery so that you can push acmeunistaller then you will have a HP Touchpad with WebOS only were you can reinstall the rom from acmeinstall2 or acmeinstall3. I had the same issuse.
thanks!
After much trial and error, I was able to reset the touchpad and install my fave ROM (schizoid). The instructions in the posted threads weren't that great on details, but the answers I was looking for were found in deep in those threads. Thanks again for all the help!:good
:good:
chrisms1973 said:
After much trial and error, I was able to reset the touchpad and install my fave ROM (schizoid). The instructions in the posted threads weren't that great on details, but the answers I was looking for were found in deep in those threads. Thanks again for all the help!:good
:good:
Click to expand...
Click to collapse
It would be useful if you could say exactly what steps you took to make it easier for anyone else that may experience a similar problem.
sstar said:
It would be useful if you could say exactly what steps you took to make it easier for anyone else that may experience a similar problem.
Click to expand...
Click to collapse
First i did all the steps up to the "open Novaterm", since i was having trouble with it(like many other people). After that, i followed the instructions found at the top of page 12 in that thread. this got me to a fresh start so that i could install acmeinstaller3 and any rom. Good Luck.
I was rooted on 7.3.0 from the day I got my replacement kfhd less than a month ago. I forgot to turn off automatic updates and yesterday 7.3.1 installed and immediately I'm having problems. Some apps I had installed are gone, like No Lock and Apex Launcher (I'm almost positive that's which one I was using) for starters. I tried to reinstall No Lock since I have Nova Launcher working and I'm sick of unlocking twice. Downloaded No Lock, went into ES File Explorer to move it, and there is NOTHING in /data/app to move.
I'm almost afraid to see what other problems there are. I downloaded a root checker and it says I'm not rooted anymore. Well that explains a lot. However Google Play has hung around problem free, which you did need root for.
How should I proceed? I fried my fiancee's kfhd a month ago after I rooted it. I was attempting to install TWRP, screwed up, and bricked it. She went out and bought another tablet. I called Amazon and told them it just died for no reason so they sent a replacement which became mine. If I brick another kfhd I don't think Amazon is going to want to replace it again.
I know 7.3.1 was just sent OTA and not to everyone a few days ago (found that info on the forum somewhere) so has anyone re-rooted after getting it? What other things can I safely try?
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
MightyBraeburn said:
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
Click to expand...
Click to collapse
Rooting it again would probably work from what I know about rooting phones. I'm kinda hoping someone else has already done it so I know for certain that it's gonna work before I do it.
Maybe I have to be the person who finds out if simply rooting again fixes the issue.
Rooting again should fix the problem. I would try that first.
Worst case scenario it doesn't help and you have to do a factory restore or re-flash in which case you can simply restore a clean copy and then either disable the OTA updates or else, better yet, let it update all the way to 7.2.3 and then root the latest version.
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
SGoatS said:
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
Click to expand...
Click to collapse
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
-a- said:
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Click to expand...
Click to collapse
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
SGoatS said:
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
Click to expand...
Click to collapse
You're welcome.
Sent From my Kindle Fire HD running CM10.1
Hello, I have a Kindle Fire HD 7" running the downgraded 7.2.3 from KFFA. Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo.
My screen doesn't do the "White haze" that others have mentioned.
Still boots into recovery allowing for wipes + installs.
I have reverted back to 100% stock then made my way back to stock + TWRP three times now, and have looked rather extensively through any threads even somewhat relative to my own problem.
I've been using the Factory fastboot cable to get into fastboot if that makes any difference.
I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before.
ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)
Have tried my cable from my Note 2, Captivate, Epic 4G Touch, and stock KFHD 7" cable as well as the factory fastboot cable.
Kinda stuck, have gone round like this for about 4 hours + now and I must say, the KFHD 7" has been the biggest pain out of any of my Androids by far xD Great tab though.
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
If I left out anything, please, let me know and I will respond ASAP.
veladem said:
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
Click to expand...
Click to collapse
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
veladem said:
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
Click to expand...
Click to collapse
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
LinearEquation said:
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
Click to expand...
Click to collapse
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
veladem said:
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
Click to expand...
Click to collapse
You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS. Just drag and drop ROM onto internal SD card before booting into TWRP.
LinearEquation said:
You never said you could access an OS. You simply said you could not get past TWRP. You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS.
Click to expand...
Click to collapse
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
veladem said:
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
Click to expand...
Click to collapse
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
LinearEquation said:
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
Click to expand...
Click to collapse
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
veladem said:
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
Click to expand...
Click to collapse
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
LinearEquation said:
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
Click to expand...
Click to collapse
I give back to the community by offering free Android and iPhone modding in my area, and free support via text and email.
Plus I make sure to tell them to check out the Dev's thread or website and to consider donating to the people who make the magic happen.
The only service I make people pay for is electronic repairs which is a flat rate of $20 + customer buys the parts.
So I think I give back to the community at least a little seeing as I have at the least 20+ people a month asking for help cause some idiot installed a unstable ROM on their phone and 4G vanished or other problems.
By the way, since we are laying our d*cks on the table, might I add that boasting about how many "Likes" you have or "Thanks" isn't something to be proud of, you earned them yes, but don't shove that in other peoples faces, that's just childish.
Thanks again for trying to help.
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did try that yes.
Thank you for helping btw.
It's water under the bridge for me. Would be funny if that were the case though because asking him if he swiped was one of my initial responses to him.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes sir I did.
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Sucess! Kinda :/
stunts513 said:
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did verify that it is on stock, rooted, de-self updater-ed, 7.2.3. It was on 7.3 something originally.
Hellfire flashed over just fine, CM 10.1 (I think) Flashed it, booted KindleFire (Orange) then (Blue) then Boot logo Booted pretty fast too.
mrkhigh said:
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, 2012 KFHD 7" (Tate)
Yes, TWRP works fine.
No, I got Hellfire to flash, but so far nothing else will flash 0.o :/
Also, I did all my restores from KFFA, BUT, I did do a original backup via ADB and did a restore via Fastboot thinking it might have been KFFA but no go still.
And yes, the thread kinda goes to poop cause I was already kinda upset cause this has been the most frastrating Android to work with, and then the pressure got compounded just cause I decided to ask for help :/
If any of this info helps, please let me know, I believe Hellfire is CM 10.1 . . . I believe, that's off the top of my head though.
Thanks!
To be honest I've only installed kinology... Wife won't let me get rid of the kindle os. I didn't really needed kinology but I wanted to update and did not want to reset it up again. He basically ran a neater version of what I was doing.
Is there an error when you flash the ROM and what ROM are you flashing
Sent from my XT907 using xda app-developers app
I had a TF701T tablet and dock I sold on ebay. It was neither rooted nor unlocked and worked fine. The buyer later complained saying it didnt work right, wouldn't read the SD nor an external drive. Now i know to read a external drive it needs to be rooted. But I advised it worked perfectly when it was sold. He filed a PP claim. It got here and guess what, it doesnt work right because he unloaded the bootloader flashed CWM on it. IDK what else was done but he lost the PP claim and rightfully so. But with that being said, the tablet would not turn off so eventually it will die. It will charge though. Where would I begin in flashing (I assume) the OEM software to make it usuable again?
Sounds like your buyer was a straight up dumbass.
The first thing I think you need to do is check the forum for the updated bootloader and recovery and go from there if you can install them. If you can't, idk.
You begin by determining which bootloader version you currently have: Boot holding Power and Volume Down until you see some small text. Let go, read the text and post it. Do not use the Wipe Data option from that page with CWM installed!!!!!!!!
Next you need to find the corresponding stock recovery (same firmware version) at Droidbasement and flash it in fastboot.
That done you download the Asus firmware for your SKU, unzip that file once resulting in another zip. If the tablet boots into Android, you can copy the second zip to the root of your internal storage. You should get a notification that an update is available. Confirm it and the stock recovery will flash it. That'll put you back onto stock. But there is no way to relock the bootloader - sorry.
If that does not work there's also a way to flash the stock firmware from a microSD. Let me know.
I wrote a pretty detailed guide on flashing a recovery and rom for the TF700. It's the first sticky in the TF700 General section.
Read that for the basics on getting fastboot to work.
The TF701 is very similar to the the TF700, but there are small but important differences and I wrote that guide for people trying to get AWAY from stock, so you're gonna have to extrapolate. But the basic steps are the same.
Ask here if not sure and flash only once you are clear on each step.
An easier option would be to flash one of sbdag's stock Asus roms. You still have to determine which bootloader you have now and if your CWM version is compatible. But if both are ok, you could just flash the rom and would be on pure Asus stock, but rooted with a custom recovery and could try to sell it as such.
There may be people who actually looking for a tablet all ready for flashing custom roms to it...
Lets face it: Nobody knows what that guy did to the tablet and you should disclose that to the next buyer. So I think you have a better chance to sell it to someone who wants to tinker with it. Swappa would be a good place for that.
Thanks guys. I finally got this back working.
weedahoe said:
Thanks guys. I finally got this back working.
Click to expand...
Click to collapse
Out of curiosity: How?
In the end, a data wipe though CWM that was installed by the buyer.
Thank God it was simple.