I upgraded to ICS official version with official update that claimed to fix reboot issue.....it didnt so I tried evolver 1.3 and 1.3.1 and got random reboots and power offs too.
I had enough so I reverted to revolver 3.11.1 and was still having reboots even though I did full wipes. So I ran the super wipe script which kills all ? and I am still getting reboots and power offs so what else can I do ? some have said that its the ICS bootloader that has screwed everything so how can I get the HC bootloader back ? Or any other suggestions?
When I found myself in this situation, I found that if I NVFlash a stock honeycomb image first, all is stable again.... I posted a 10 step guide to return to Honeycomb, but you can only NVFlash with theolder Transfomers - is you device NVFlash'able?
Sent from my Transformer TF101 using Tapatalk 2
still on the icys bootloader?
Sent from my Transformer TF101 using XDA Premium HD app
If you were willing to flash a custom ROM, you probably might as well also try Guevor's custom kernel. A bit late now, since you already went back to Honeycomb.
jtrosky said:
When I found myself in this situation, I found that if I NVFlash a stock honeycomb image first, all is stable again.... I posted a 10 step guide to return to Honeycomb, but you can only NVFlash with theolder Transfomers - is you device NVFlash'able?
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I have not tried that yet.
I have B60 so I can nvflash.
As far as I can tell the main issue with ics is it doesn't like deep sleep because the guvnor kernel disables deep sleep which I guess uses more battery power well thats what I found with version 14 and I still had 1 reboot too.
Thanks for advice guys.
Do you have a link for guide ?
grandmaster_b said:
Thanks I have not tried that yet.
I have B60 so I can nvflash.
As far as I can tell the main issue with ics is it doesn't like deep sleep because the guvnor kernel disables deep sleep which I guess uses more battery power well thats what I found with version 14 and I still had 1 reboot too.
Thanks for advice guys.
Do you have a link for guide ?
Click to expand...
Click to collapse
Search jtrosky's forum posts for that guide.
Here is a link to the quick 10 step guide I put together real quick. Links to stock firmware and root'ing util are provider there as well...
Good luck!
http://forum.xda-developers.com/showthread.php?p=24576480
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
Here is a link to the quick 10 step guide I put together real quick. Links to stock firmware and root'ing util are provider there as well...
Good luck!
http://forum.xda-developers.com/showthread.php?p=24576480
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot I got the file and will nvflash back to old faithful HC until they solve this rebooting nonsense
Does the nvflash replace the ICS bootloader ? because I think thats all that could be left causing the issue from my ICS update ? So just wonding how it is going to fix the reboot issue by flashing..........not doubting it does but just wondering how.
grandmaster_b said:
Thanks a lot I got the file and will nvflash back to old faithful HC until they solve this rebooting nonsense
Does the nvflash replace the ICS bootloader ? because I think thats all that could be left causing the issue from my ICS update ? So just wonding how it is going to fix the reboot issue by flashing..........not doubting it does but just wondering how.
Click to expand...
Click to collapse
It does replace the bootloader, although, we've done some testing that also suggests that the bootloader is NOT what it causing the issues in ICS...
I wish I knew what the difference was - keep in mind that there are like 15 or 16 partitions on the iternal memory. NVFlash re-creates them all, I believe, whereas most CWM packages only flash a few of those partitions.
However, I agee - if we can determine what NVflash does differently than CWM when flashing Revolver, it would be a big help in determining where the problem is!
Multiple folks have reported success with the NVFLash method (I haven't seen anyone say that it hasn't worked). I actually learned of it from another post on the forum myself....
jtrosky said:
It does replace the bootloader, although, we've done some testing that also suggests that the bootloader is NOT what it causing the issues in ICS...
I wish I knew what the difference was - keep in mind that there are like 15 or 16 partitions on the iternal memory. NVFlash re-creates them all, I believe, whereas most CWM packages only flash a few of those partitions.
However, I agee - if we can determine what NVflash does differently than CWM when flashing Revolver, it would be a big help in determining where the problem is!
Multiple folks have reported success with the NVFLash method (I haven't seen anyone say that it hasn't worked). I actually learned of it from another post on the forum myself....
Click to expand...
Click to collapse
Exactly it has to differ some how so it would be nice to know in what way.
Anway as it has worked for all so far I am hoping to flash back tonight if I get the time and I will post my results after a few days to make sure the reboots have gone
Thanks again for your advice and help !
I performed the Nvflash to stock then rooted and used clockworkmod to install Revolver 3.11.1 and as before the ICS fiasco it looks to be resolved because my TF101 is still alive this morning no power off as it was doing before nvflash restore and no reboots at all.
I did notice that nvflash does create quite a few partitions and also does flash the HC bootloader so it has to be structure or bootloader that is the problem then because the kernel is taken out of the equation if I done a super wipe on my TF101 and installed HC with stock kernel.
Related
anyone tried this ROM already on A500 ?
Thor Transformer Revolver 3.2.1 Port V3
proxonic said:
anyone tried this ROM already on A500 ?
Thor Transformer Revolver 3.2.1 Port V3
Click to expand...
Click to collapse
It's been updated to V4. It seems pretty solid but that's less than 24 hours of usage. I think I've got OC to 1.5 or 1.6, no problems. As noted at his site, Auto Brightness does not work. I'm interested in GPS so not sure if that is supported or not. So far, so good with the ROM. I may give Taboonay another go, but feel comfortable with Thor's ROM. Also, Netflix does not work. I don't think it found it on the Market but I tried restoring from a backup and got an FC. I believe this is a known prob with HC 3.2.
i tried it, one hour later I was back on Taboonay v.2.1b.
also, when leaving it, wipe everything atleast 5 times, or your wallpaper wont work no matter what
leo72793 said:
i tried it, one hour later I was back on Taboonay v.2.1b.
also, when leaving it, wipe everything atleast 5 times, or your wallpaper wont work no matter what
Click to expand...
Click to collapse
Interesting. I tried Taboonay and didn't like it. I had some issues with OC with Thor's and am now giving PRIMEE P9-5a a go. It's better but thinking I may not stick with it. Perhaps I'll give Taboonay another go.
I did not like it at first either. Once I oc it was better. Make sure you use the 2.1b version.
Sent from my PG86100 using XDA App
Thor ROM updated to v4.1
looking335 said:
Interesting. I tried Taboonay and didn't like it. I had some issues with OC with Thor's and am now giving PRIMEE P9-5a a go. It's better but thinking I may not stick with it. Perhaps I'll give Taboonay another go.
Click to expand...
Click to collapse
I tried this too, but to my dismay when i reverted to my back up of Taboonay 2.1b, I lost root priviledges!!!!!!!! Unable to access the cwm, or anything that involves root. I have been searching for hours now for my fix. To no avail.
Wipe all partitions and dalvik before restore. It works.
Sent from my PG86100 using XDA App
Im stuck without su priviledges now. No cwm recovery, no acer recovery.
Im at a loss on how to fix this.
Sent from my A500 using xda premium
are you able to get into cwm recovery by pushing power and volume down buttons during bootup?
if yes - just put some 3.1 rom on your sd card and flash with it.
honeyvilain 1.05a was for me great choice.
proxonic
No, i tried vol up and pow and vol down and pow. No luck either way....
Sent from my A500 using xda premium
Edit: i tried it again, this time holding it longer, or maybe holding my mouth the right way... either way cwm is working now
leo72793 said:
I did not like it at first either. Once I oc it was better. Make sure you use the 2.1b version.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Thanks, I did try it (twice) with the 2.1b. I've tried pretty much all of the HC 3.2 releases minus the minimal custom ROMs but seem to like Falcon Acer HC 3.2. I noticed some oddities when I maxed out OC so running at 1.5 seems to make for a solid ROM. I didn't have a chance to fully test GPS. I'm using richard's kernal but may try thor's.
---------- Post added at 01:26 AM ---------- Previous post was at 01:22 AM ----------
Rainbowbright081 said:
Im stuck without su priviledges now. No cwm recovery, no acer recovery.
Im at a loss on how to fix this.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
I would:
1) Root your device with the tools already out there (I used ioniaroot)
2) Download Acer Recovery from Market and install CWM through that. Unless it has been updated, it will not give you the latest CWM, which you can download, install on your SD card, and flash from CWM
Keep us posted
So, I simply flashed another Rom. After of course figuring out that my recovery was still there.
All is well again!
Sent from my HTC Glacier using XDA App
Yeah, had the same issue when flashing my recovery image back to taboonay. Had to actually reflash the original taboonay rom and thor kernal. The recovery loses root for some reason.
Unfortunately, Revolver lacks 501 support, even after messing with the build.prop and an additional lib file. And Thor doesn't have a 501 to play with.
Looked promising though, a little more responsive than taboonay.
Rainbowbright081 said:
So, I simply flashed another Rom. After of course figuring out that my recovery was still there.
All is well again!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Rainbowbright, glad you back in action with your tablet. It seems thor has released an update to this ROM so very tempted to give it a whack this weekend, though I am really enjoying Falcon's Acer HC 3.2 ROM.
---------- Post added at 03:27 AM ---------- Previous post was at 03:25 AM ----------
Moscow Desire said:
Yeah, had the same issue when flashing my recovery image back to taboonay. Had to actually reflash the original taboonay rom and thor kernal. The recovery loses root for some reason.
Unfortunately, Revolver lacks 501 support, even after messing with the build.prop and an additional lib file. And Thor doesn't have a 501 to play with.
Looked promising though, a little more responsive than taboonay.
Click to expand...
Click to collapse
Interesting you say that about Taboonay. I was trying to figure out why I didn't stick with it given its popularity and remembered that was my experience as well. I have a USB 3G pay-as-you-go modem and have read those devices are supported, so I opted for the 500.
Hi
To be able to bypass the process of a flash to v13_13, open the backdoor, flash to 14_14 etc. can anyone point me to a rooted 14_14 rom?
In particular "K1_A301_14_14_120109_US"
Thanks
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
Although still in the alpha stage, I switched from using timmydean's rom to this one specifically so I could successfully run the 14_14 rom and keep my root. Nothing against timmydean and his work, this just worked easier and faster. Also this rom add cwm which is the only rom out currently that does this for the k1, from what I've seen.
Just reemeber that this is still just an alpha, so be sure to read the post fully. Hope this helps!
Thanks for posting the link Dueces99. I compiled the CWM and ROM that Deuces99 linked to. I just wanted to add that there is nothing alpha about the ROM, just CWM. The ROM is stock and rooted and has no bugs (Other than the ones the stock ROM has).
The reason I left the Alpha status is because backup/restore don't work in CWM, and there is currently no key combination to boot into recovery. You must boot to recovery using the included app/widget
Right, there is no physical key combo. associated to booting into Recovery, the rom atleast provides the means to boot into recovery (widget/app) which atleast leaves the option. I personally, have not had any issues at all with this rom, and love the fact that all the bloatware misc. 3rd party apps and some Lenovo apps were removed, which made the rom seem that much more responsive upon first boot IMO.
Glad to hear that was of some help to you, kinda surprised there hasnt been anyother spinoff roms from this, regardless of its released stage. Just how cut and dry it is with flashing the 2nd newest update with root, then simply flashing the 14_14 update through CWM and keeping root. That was my biggest hurdle following timmydean's guide (and still is) was keeping root once taking the update from Lenovo.
Just my 0.02
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
prfstrkr said:
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Correct. After that you will be up to date and rooted.
Right, confirming with khanning88 flashing alpha 3 would be the 13_13 update. After flashing that, reboot into recovery via the Reboot Recovery app/widget included in the ROM, follow the instructions from there provided by the rootzwiki post and you'll be good to go with the latest 14_14 update. By far, the most cut-n-dry rooted ROM out there as far as I know. IMHO kinda deceiving that the ROM is listed as an Alpha (for CWM understandably) only because it's been extremely stable for me with nada one FC.
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Dueces99 said:
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Click to expand...
Click to collapse
From what I understand, it's the same firmware as the stock Lenovo, so maybe a little bit of a placebo effect? The CWM ROM does take out all the built-in non-Google apps, so maybe that has something to do with it.
I hope Lenovo gets its act together and shares out the proper source code so that some good samaritan out there can build a stock Android ROM to run on the K1. I've been using it a bit on the 14_14 CWM firmware, and it's still not as good as the firmware I've experienced on the ASUS Transformer TF101 or the Acer Iconia A500. The biggest issue I've found with the Lenovo firmware is that there is a lag closing out of apps and going back to the launcher, sometimes to the point that a forceclose-wait window pops up. I've not experienced that on the Honeycomb ROMs of any of those other two devices, so I wonder if it's because of Lenovo's customizations to Honeycomb, like the ability to close apps from the multitasking sidebar. In that case, maybe a more vanilla version of Honeycomb won't have that problem. Don't get me wrong; I think it's a great feature that Lenovo added to the taskswitcher. But I'd rather not have it than have the operating system lag. I trust Android's memory management enough to not really need to go manually closing apps.
Right, im sure all the bloatware taken out from Lenovo had to have some effect on overall performance. As far as stability between the two, maybe I meant to say "Wierd how an alpha build ROM feels more stable than the OS that the K1 comes with..."
But placebo effect or not, I've experienced zero issues with this rom even though I probably don't do near as much as other K1 owners with their tab. Lenovo does need to fix this, or preferably just provide full source to all...
khanning88 said:
Correct. After that you will be up to date and rooted.
Click to expand...
Click to collapse
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
prfstrkr said:
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
Click to expand...
Click to collapse
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
I'm glad I remembered to check back on my thread!
I'll be a rooting tomorrow morning
Thanks Dueces99
omg ... plz tell me it's ICS
Sent from my Xoom using xda premium
khanning88 said:
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
Click to expand...
Click to collapse
Thank you so much, khanning, for all of your efforts. As I mentioned in this thread http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285 , your CWM firmware is the only effective workaround at the moment for those of us whose K1's are inexplicably locking up with "unrecoverable bootloader" errors to get onto the latest firmware.
We still aren't completely out of the woods though. In post 44 of your rootzwiki thread http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__390175 and post 47 http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__392343 , the users kennethrkennedy and aig787 both confirm that the "unrecoverable bootloader error" can still come back with updates, even through your CWM recovery. With your Alpha3 and your 120109.zip update, you managed to avoid updating whatever it is that causes the "unrecoverable bootloader error." This is my long rambling plea that, whatever you did there, you will continue to do for the latest update you are working on, so that those of us with these K1's that are prone to the "unrecoverable bootloader errors" can join the fun too. Thanks!
Hey people,
Currently I was running AOKP Build 33, then decided to flash my Transformer's kernel to Clemsyn-Blades3.2OCver22a (http://forum.xda-developers.com/archive/index.php/t-1109630.html), now it seems to be stuck on the Asus EEE Pad screen. I did a back up and through CWM v5.8.1.8 and restored without problem but it's still stuck.
I'm out of ideas and hoping you guys have some
gurellaz696 said:
Hey people,
Currently I was running AOKP Build 33, then decided to flash my Transformer's kernel to Clemsyn-Blades3.2OCver22a (http://forum.xda-developers.com/archive/index.php/t-1109630.html), now it seems to be stuck on the Asus EEE Pad screen. I did a back up and through CWM v5.8.1.8 and restored without problem but it's still stuck.
I'm out of ideas and hoping you guys have some
Click to expand...
Click to collapse
The Blade kernel is for Honeycomb. It is not compatible with ICS. You can reflash your ROM to get the original kernel back.
kokopopz said:
The Blade kernel is for Honeycomb. It is not compatible with ICS. You can reflash your ROM to get the original kernel back.
Click to expand...
Click to collapse
oh dman, is there a way I can put the original files to the internal memory, or update via SD card. my computer won't recognise the device when I plug it in
Yes use ADB and next time don't just random flash things. True guevor's kernel (I really have no idea why you haven't used that one .....)
gkillerx said:
Yes use ADB and next time don't just random flash things. True guevor's kernel (I really have no idea why you haven't used that one .....)
Click to expand...
Click to collapse
I second guevor's kernel. I was having the random reboots from anywhere between a few hours and less than two days, and since I flashed test13 I haven't had a single RR or SOD in two weeks.
Quick question:
Is the guevor's kernel compatible to stock ICS build 9.2.1.17??
It's rooted with CWM installed.
gkillerx said:
Yes use ADB and next time don't just random flash things. True guevor's kernel (I really have no idea why you haven't used that one .....)
Click to expand...
Click to collapse
Where can I download the kernel from?
I managed to use ADB to push then flash back to stock it's all working fine now.
gurellaz696 said:
Where can I download the kernel from?
I managed to use ADB to push then flash back to stock it's all working fine now.
Click to expand...
Click to collapse
its in the development section
farsight73 said:
Quick question:
Is the guevor's kernel compatible to stock ICS build 9.2.1.17??
It's rooted with CWM installed.
Click to expand...
Click to collapse
Yes, it's fully compatible, tried it myself not that long ago.
its under test 16b it works perfect
Sent from my Transformer TF101 using XDA
okay well I managed to upgrade to milestone 5, flashed guevor's kernel 17c and now it all works fine
Good To Hear
Thats good to hear. But make sure next time you read ALOT before flashing something!!!!!
sandman7793 said:
Thats good to hear. But make sure next time you read ALOT before flashing something!!!!!
Click to expand...
Click to collapse
yea that's the last time I'm flashing something when I'm half asleep
Hello TPT community,
I Just got this tablet mainly because of the included digitizer and was wondering if anyone could give me a guideline on how to speed things up for this tablet. The tablet came with honeycomb 3.1 included and I am finding it pretty sluggish and unresponsive in general tasks. I went into settings to do a software update but it seems there is no 4.0 update available. There doesn't seem to be a toggle for pen only input in the settings either. Is the normal process for flashing a new Rom to root, then install CWM, and flash Roms?
I'm kind of a n00b here, but that is the right process in general.
For you, there should be a 4.0 update, but you might have to try a few times. After you are running ICS (4.0) you can root and load Koshu's JB rom.
Aren't there problems with rooting ICS?
Sent from my ThinkPad Tablet using xda app-developers app
Absolutely no problms rooting ics
Sent from my Micromax A50
Okay well I went into settings, about tablet, system updates, check for updates. It always says "your system is up to date" even though I know I'm on 3.1
Sent from my ThinkPad Tablet using xda app-developers app
Lets see if we can figure out why it won't update. In settings -> about tablet, what is listed for model number, android version, and kernel version?
Edit:
Found this - http://forums.lenovo.com/t5/ThinkPa...ystem-updates-OTAs-not-installing/ta-p/713571
It might help... I'm also searching for a manual download for ota3 or ota 3.5 from lenovo that you can load in recovery.
Edit 2:
Sorry, I need more coffee...
Is this a wifi only tablet or a 3g tablet? What region is it?
I attached the info in a picture. I dont know how to find out what region or wifi/3g it is though. I don't have a sim to test it. I got it from here: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=7473177&CatId=6845
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
da_reeseboy said:
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
Click to expand...
Click to collapse
So any ideas on how to update to ICS? The ROM in android development section says it requires me to have ICS first.
Unfortunately no... sorry. I'm still a n00b with android devices. Maybe someone with a little more knowledge will chime in now that we know what we are dealing with.
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
troemer said:
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
Click to expand...
Click to collapse
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
@troemer: Not sure if you noticed it or not, but in Koshu's cm10 thread it says:
Requirements
This build uses the Lenovo ICS kernel, you need to upgrade to stock ICS first (Make sure you keep root!)
Click to expand...
Click to collapse
This is why he is trying to get the ICS update.
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
Click to expand...
Click to collapse
The wifi bug actually isn't that big, just set wifi to always on like suggested. As far as the tampered drivers error, you will probably have to : a) search for a way to install unsigned drivers on win8
or b) use a winxp/win7 pc.
Be careful tho... flashing after having stock ICS is needed for a reason.
Flashing what?
Daedalus_ said:
Flashing what?
Click to expand...
Click to collapse
Based on this:
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
Click to expand...
Click to collapse
I was worried you were gonna try to just jump straight to JB.
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
It looks like there's hope - this guy has the same weird software version as you - http://forum.xda-developers.com/showpost.php?p=37487649&postcount=6. He used the directions in that thread to upgrade to ICS.
Edit -
Full thread: http://forum.xda-developers.com/showthread.php?p=37487649#post37487649
Koshu said:
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
Click to expand...
Click to collapse
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
da_reeseboy said:
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
Click to expand...
Click to collapse
Thanks for still helping! Do I need a special CWM? I just root and install CWM from the market? Honeycomb is really annoying because some apps I use are only for newer androids such as Hulu plus.
Goooooooooooooooooooood News...
Finally Found A Way To Unbrick The Tab, Which Requires Mainboard Replacement!
As You Know, If You Have Installed Wrong TWPR Recovery On 4.2 Update, And By Accident Have Erased Recovery Partition, Then You Would Have A HARD-Bricked Tab Which Showed: "Unrecoverable Bootloader Error"
In This State, Asus Support Center Required You To Pay (As You Are Unlocked) To Replace The Mainboard!!!
Finally, One Of Our Friends Found A Solution, Here Is The Link, I Just Wanted To Spread The Word...
It Saved My TF300T, Which Has Been Turned Off For 6 Months!
Here Is The Link, Just Be Patient And You Will Recover Your Tablet
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
wow man if this is true I'll unlock my bootloader and flash a custom rom even today!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
it could easily recover my tab, which was supposed to be sent to Asus next week
it's a milestone, greatly helped...
wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
you saved hundreds of dollars for us, i wish i could donate
i just can say: "I DO APPRECIATE" <3
thanks more than a million, bro
Best fix ever.
Thanks !
:good::good:
therock3181 said:
Best fix ever.
Thanks !
:good::good:
Click to expand...
Click to collapse
press "Thanks" button if it helped
this! a thousand times this!
i'm hitting the thanks button like its going out of style, will see about donating as you just saved my brick from 5 months of staying in a cabinet!
this needs to be sticked, or the original post! holy crap i am happy
This is how i unbricked mine. Try it.
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
How to uninstall or remove TWRP recovery from tf300?
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail
Thanks you just save my tf
interslicer said:
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail
Click to expand...
Click to collapse
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.
snoopspecial said:
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.
Click to expand...
Click to collapse
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
So it is a really good idea to backup your device prior to bricking it , to backup your device, use flatline (google it. sorry for not providing the link, this forum does not allow me to post links yet)
Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
As far as I can tell Vol+ gets me the black screen and recognized as a device in Windows 7 x64 as an ASUS APX Interface. I tried replacing the driver with every combination of NVIDIA, Google, Android SDK, Naked .72/.73 and no go. I've also tried ADB drivers and no luck there either.
Vol- doesn't bring up anything - screen just stays at ASUS logo. I dont get the recovery menu and can't get into TWRP (original) or CWM (after attempting to install). My mistake for not just sticking with TWRP (previously on 2.6.0.0) and using the scannos version.
It basically gets to the Device is Unlock, ASUS and NVIDIA logo and doesn't proceed further.
Any ideas?
Thanks in advance.
with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
neither - i dont ever get to that.
Same here - stuck at the first ASUS logo - in the left corner "the device is unlocked" and right corner the Nvidia logo.
Vol+ and power or Vol- and power - no effect.
I flashed an old recovery using adb commands in a newer twrp so is there any way to fix this?????
Sent from my LG-E980 using Tapatalk