Hi,
Firstly, I sincerely apologise for another thread like this. I have searched, and done all that stuff, and I have a good idea of the situation in my head, but so often I get these things wrong, I just wanna get confirmation.
I bought a TF101 for Christmas after the UK price drop and it's a B90 device. I understand that as it currently stands, this means it can be rooted and CWM installed, and ROMs such as Prime and Revolver can be installed, but if anything goes wrong, there is no fallback because NVflash doesn't work.
I was just wondering, firstly is this indeed the case? And secondly, have there actually been any reports of B70+ devices being completely bricked with no fix?
I really wanna get a custom ROM, but I'm very aware that while CWM is better than no recovery at all, if anything were to corrupt it, I'd be stuck with no fallback at all, and a useless £300 spent.
What situations may lead to it becoming bricked? I'm guessing it would take the complete destruction of CWM to totally brick?
Sorry for all the questions! I just really want confirmation that I'm right, advice, and a good starting place so I can try and get involved in this community
Also, just a daft thought, but if anything does go wrong and the device bricks, is there no way to use the downloadable files from ASUS and flash them to get back to stock system and recovery?
I'm not quite sure, but I think it would be fairly hard to completely brick it. If your ROM somehow gets corrupted you should be able to restore/factory reset it from either CWM or the stock recovery, and if the recovery partition gets corrupted you should be able to reflash it from within the ROM, like one does when rooting with Razorclaw.
You can use CWM to reflash the stock ROM and recovery:
http://forum.xda-developers.com/showthread.php?t=1093403
http://forum.xda-developers.com/showthread.php?t=1154947
If your CWM/Recovery and ROM are completely corrupted and/or unbootable, then AFAIK the only way to restore it is by using NVFlash, which isn't possible in your case, or RMA'ing it to Asus.
Someone with more experience could probably give you a better answer.
Hellrespawn said:
I'm not quite sure, but I think it would be fairly hard to completely brick it. If your ROM somehow gets corrupted you should be able to restore/factory reset it from either CWM or the stock recovery, and if the recovery partition gets corrupted you should be able to reflash it from within the ROM, like one does when rooting with Razorclaw.
You can use CWM to reflash the stock ROM and recovery:
http://forum.xda-developers.com/showthread.php?t=1093403
http://forum.xda-developers.com/showthread.php?t=1154947
If your CWM/Recovery and ROM are completely corrupted and/or unbootable, then AFAIK the only way to restore it is by using NVFlash, which isn't possible in your case, or RMA'ing it to Asus.
Someone with more experience could probably give you a better answer.
Click to expand...
Click to collapse
Hey thanks for the reply! Basically I'm thinking if I install CWM and a ROM, and just install updates for that ROM and avoid doing much more messing about than that, I shouldn't run into problems.
I rooted using Razorclaw, installed CWM with http://forum.xda-developers.com/showthread.php?t=1346180 and then flashed Revolver and haven't had any trouble.
Hellrespawn said:
I rooted using Razorclaw, installed CWM with http://forum.xda-developers.com/showthread.php?t=1346180 and then flashed Revolver and haven't had any trouble.
Click to expand...
Click to collapse
Is yours a B90 too?
Where do you see the B90 or B70 on the tablet...just got mine and want to check since I see a lot of people using these codes to describe their model number.
SiNJiN76 said:
Where do you see the B90 or B70 on the tablet...just got mine and want to check since I see a lot of people using these codes to describe their model number.
Click to expand...
Click to collapse
Your serial number will be of the form BXY-xxxxxx with XY being 40, 70, 90 etc. It's on the box and should be on the sticker on the back of your TF
jtc42 said:
Is yours a B90 too?
Click to expand...
Click to collapse
I have one of the later B70's, so no NVFlash support.
jtc42 said:
Your serial number will be of the form BXY-xxxxxx with XY being 40, 70, 90 etc. It's on the box and should be on the sticker on the back of your TF
Click to expand...
Click to collapse
Ah. Thanks. I was looking in the tablet at the about tablet screen. Guess I've got the B90.
Guess B90 is the latest release...too bad they never bothered fixing the left speaker.
By the way...What will brick the TABLET? I know in phones...messing up the flash of a Radio will brick the phone...but other than that...as long as you can get into recovery...everything else is repairable...more or less.
It's if you somehow mess up recovery AND system at the same time. Normally not a problem with an external flash app, but with B70+ if that happens, that's it, end of the line.
Wouldn't be worried except in my head, ICS updates, via CWM, are big enough to somehow increase the bricking risk. I might wait until official ICS OTA, and then hope we get root on that :/ I really don't know.
REALLY don't wanna brick it, and while its a very small risk, i'm all nervous still
Sent from my LT15i using XDA App
Related
Hello guys, I've got a weird problem. I messed around with my Transformer a bit, rooted etc on 8.4.4.11. CWM isn't working, and I can't even boot into recovery. It just sits at the "Loading recovery kernel...". Anyway, its freezing at the eeePad screen on bootup and doesn't do anything (this has stopped me from reflashing a blob, or Asus OTA updating). I've tried reflashing stock and rooted images quite a few times, but it always does the same thing. Now, I can get around the freeze by going to the hard reset screen and declining, and it boots into Android.
Whats wrong? Bootloader? Has to be something in startup, but I cant figure it out.
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
bud77 said:
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
Click to expand...
Click to collapse
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
EDIT: Fixed it, I had the wrong type of ROM unpacked. Thanks Bud.
padd3r said:
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
Click to expand...
Click to collapse
How could it make it worse .... ?
What's the error you're getting while NVFlashing ?
For the stock, if you can't NVFlash a rom, you won't be able to flash stock too, as the process is identical
http://androidcentral.com/team-hydro-bootmanager-coming-soon-puts-end-bootloops-forever-hacking
Very interesting... so if we get stuck in a bootloop we could just recover from a Nandroid backup without having to revert to stock, etc.
Sent from my MB865 with Tapatalk... pardon my swype!
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
I am pretty sure my phone was bootloop and how would you get it into recovery right now? i had to use the fastboot files to do it. it is a good idea though
jimbridgman said:
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
cogeary said:
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
Click to expand...
Click to collapse
Nope, if you use the razr boot hijack, it is exactly that, a hijack. It uses several "android/Linux" binaries that it "hijacks", to allow you get into CWM, just before the android UI comes up, but after the kernel is started. To get the particular hack you mentioned, working, you will have to modify the boot image, to include the recovery on boot, that will start just before the kernel is actually started/starting.
Like others have said, that since we have the fxz it does not really matter. Since I have really been doing some serious hacking and development on this phone, I have soft bricked or boot-looped my phone I can't count how many times, and even the razr CWM on boot does not always help. A good backup from CWM, and the fxz is where it is at, and really the best solution for things like this.
Most people on this site who have this phone really should not worry too much about these things, because the likelihood of doing this is very small unless you really are doing some serious hacking or development work like lfaber06 and I are. We will usually not release something to the rest of the world without testing it first, and giving explicit directions on how to do the job without bricking the phone. For those brave souls that are trying to do some dev work, and are new to it, until we get the bootloader unlocked, again the best bet is the fxz and a good backup from CWM.
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Well u do have APX mode... is there a day to do something with that?
I7
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
krhainos said:
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Click to expand...
Click to collapse
the bold part is where I can really use some help!!!!
have a tf300t, neither unlocked nor rooted atm.... I never got an OTA after purchase, always had to manually download zip and update, i cannot even unlock the damn device!!!! some unknown network error issue, even tough m fully connected ! its begining to irritate me to the core that anyone asking me advice on what to buy , i say straight up that if its asus it will be crap don't buy it!
i can really use some help regarding this.... it looks like some serial number issue..... :'(
ASUS Rep HELP me please!
Paschalis said:
I7
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
I've been trying to figure this out. But so far nothing. I've tried flashing cm10 images in fastboot. I built a recovery and used it to try and go back to stock but it give me a mismatch error. I tried flashing cm10 in recovery and everything takes me back to asus screen. Any other ideas I could try?
I would love to be able to use my tablet again.
darthvince said:
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
Click to expand...
Click to collapse
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Paschalis said:
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
krhainos said:
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
Click to expand...
Click to collapse
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Drgravy said:
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Click to expand...
Click to collapse
I have a TWRP version for someone to test here: http://forum.xda-developers.com/showthread.php?t=1843694
Flash with fastboot.
I created an RMA request with Asus, the fellow on the phone says it's bewteen $87 to $100 to repair the OS on a device with an unlocked bootloader. This excludes the cost of you shipping Asus the tablet. However, it includes the cost of labor, diagnostic, and shipping back to you.
For those of you weighing your options, there's one answer.
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Rompf said:
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Click to expand...
Click to collapse
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
TF300T in repair in Texas as well...
krhainos said:
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
Click to expand...
Click to collapse
My TF300T is in Grapevine TX having the same exact thing done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
bjanice44 said:
My TF300T is in Grapevine TX having the same exact hting done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
Click to expand...
Click to collapse
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
krhainos said:
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Click to expand...
Click to collapse
Thanks
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What I understood is that's a partitioning difference on JB... Bricked mine too, more and more showing up on these boards... I guess the more issues will show up, the bigger the chance we can have someone fix them (Not me, that's for sure )
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Reggie777 said:
I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Click to expand...
Click to collapse
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Pretoriano80 said:
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Click to expand...
Click to collapse
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Reggie777 said:
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Click to expand...
Click to collapse
All Asus software download located here:
http://forum.xda-developers.com/showthread.php?t=1734005
All instruction how to do things here:
http://forum.xda-developers.com/showthread.php?t=1834521