attempted root and used superboot grj22 from modoco pphone is unlocked and after double clicking on indows bat file as directed phone is locked on boot x
this phone has just come back from htc with a new power switch installed and 2.3.4.
anyway could use some help daughter is upset I locked her phone.
can get to boot menu however can not get into recovery. I get a triangle with exclamation in it
thanks
Please read the Wiki, Rooting guide for unlocked bootloader.
Flash recovery through fastboot.
Flash whatever ROM you want from recovery.
You've flashed a wrong kernel (which is contained in "superboot"), that's why you can't boot.
another question
read wiki and followed instructions which said after loading passimg that this was an older version. searched more and found another thread that gave a new file that was supposed to load the older version of the rom and get around the error "older version"
still not working any other ideas will be appreciated
Just to make sure I understand right you tried the frg83 passimg file and you got "main version is older" error? If so then can I just ask you is your bootloader unlocked (at the X screen before the cyanogen mod logo do you see an unlocked padlock)?
hi
yes padlock on screen is unlocked tryed to flash again and get the same error version is older
thanks for trying to help kid leaves for school tonight and is freaking
more
also askes if I want to reboot device
It'll be long fixed by then don't worry
Boot into bootloader then from there select the recovery option. Once there tell me what you see if you see and android with a /!\ next to it then press power and vol+ power slightly before. Then you will get a menu select power down. If you go straight to the menu tell me what color the writing is.
hi
get the triangle white with a orange exclamation in it
Ok then you'll need to flash a recovery via fastboot. So since you bootloader is unlocked I assume you already have the SDK set up and the drivers installed if not then I can help you with that too, but now just download this file and place it in the same directory as fastboot on the computer and download this file and put it on the root of your sd card (not in any folders).
Then boot the phone into fastboot (hold down the trackball while powering up) then connect the phone to the computer via usb and open a command prompt in the directory where you have fastboot. Then input these commands:
fastboot devices (this should return the s/n number from your phone)
fastboot flash recovery recovery.img (where recovery.img is the name of the first file you downloaded earlier)
fastboot boot recovery.img (same thing here)
The phone should then boot into recovery from there use the trackball to navigate go to flash zip from sd card then chose zip and chose the second file you downloaded earlier (the one you put on the sd card), after that wait for it to flash then press vol- to go back to the recovery main menu then select reboot system now and your all good you have stock with root access, if you want to flash a custom ROM then just ask I can explain that too.
As I've said, follow the guide FOR UNLOCKED BOOTLOADER.
You didn't.
The guide for unlocked bootloader is in Unroot/Restore section, called "using fastboot".
Actually, the only thing you need to do is to install recovery. Go to "recovery" guide - again, FOR UNLOCKED BOOTLOADER - and install Amon_Ra's recovery.
Once you have it, you can flash whatever you want, including stock ROM.
ok
everything is good except that i tryed to flash downloaded zip from sd and got error that zip is signed wrong also zip verifacation failed
again thanks excited I got this far.
so after this gets fixed than will phone reboot and go to 2.3.4 that was on there before?
will I be good to go for a new rom and last but least like the miuis and recommendations from an expert?
funny I bought the sensation and forgot how to do all this probably the pressure of the child (oh my god you wrecked my phone) Forgetting of course it was dads to begin with DARN KIDS
me dumb as a box of rocks toggled zip verifacation and ra unzipped.
afraid to push any buttons.
should I reboot?
and then Its ok to load a rom?
thanks
radio should be ok as it was just loaded from htc?
Ya you should be good don't worry you can't brick it by flashing something to the system partition only to the recovery and hboot partitions. Just select reboot system now and all should work fine.
Sorry for the late response I was away from my computer
still stuck on nexus x screen ??
earlier someone posted that when I used superbot I got the wrong kernel?
not sure but still stuck
just tryed to boot into recovery and it wouldnt go
Oh right sorry forgot an important step you kind of need a ROM my bad ok so forget about su you're going to need to flash a ROM I suggest cyanogen mod as a first ROM but it's up to you if you want miui or something then go for it. Here's a link to cm7 http://dl.dropbox.com/u/31690913/android%20files/update-cm-7.0.3-N1-signed.zip
So to flash this simply boot into recovery then go to wipe, wipe all at least 2X I do 5X to make sure then just go to flash zip from sd card and flash the ROM.
In that case do like we did last time and reflash it through fastboot. Now sorry but I gotta go maybe someone else can come and help you if not I'll be back later tonight.
thanks
thank you so much for helping me with this got everything working including the new miui rom.
when you panic just a little you forget all the things you knew how to do before.
thanks again.
Related
I think i bricked my phone by fallowing this tutorial.
http://forum.xda-developers.com/showpost.php?p=3874647&postcount=406
It happened after flashing the spl.
My phone will not go past the white "t-mobile g1" splash screen.
thank you for reading.
Damn, another brick? Did you make sure you had a PVT board and not the DVT-1, DVT-2 boards? It's a known problem with the Special SPL that it pretty much bricks DVT board phones...at least so far. (check by booting with camera+power if possible, board type is shown on the first line of text)
Can you boot using home+power? Are you just stuck at the Splash screen? If so, after about 10 mins the screen will change, giving you an triangle error symbol. At this point push Alt+L. This should give you the recovery utility, where you will have access to wipe (you should prob do one) and reflash a rom.
Of course this is all assuming you have root already.
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
aronissleeping said:
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
Click to expand...
Click to collapse
Ok, so what you need to do is this:
1. Wait for the error message //remember it sometimes takes 10 mins or so
2. open keyboard, hit Alt+L //this will toggle your phone to the recovery utility
3. If you have root, you may have a recovery utility that says "JF version 1.43", if not you have the stock recovery utility
4. If you have root, you could try to DL pretty much any rom although I might try the Ion rom for its stability and simplicity //there are tons of instructions for flashing a new rom
5. If no root, search in the Dev section of the Dream forum for an OTA ( Over The Air, ie. stock) rom. In particular, search for Dreaimg.nbh, and read the instructions for reflashing it. This will help you gain root.
6. reboot, and enjoy (hopefully)
If none of that works, you can find the "Bricked G1's" thread on the Dev section too. I think your prob out of luck, but it's possible someone has/or is coming close to a fix.
re flashing ill let you know the out come
lol you didnt brick it since u can access the recovery image.
anyways what happened to me yesterday, i flashed latest radio, the latest spl and it wouldnt boot. i flashed a new system image but still no boot (t-mobile screen). I wiped the system (data partition) from recovery boot, and reflashed with a new system image, worked ok... so from what i get, u need to wipe / reflash system, if you upgrade spl...
is by using a card reader on a pc the only way to flash a different img if this happens to you?
my phone is in root and i'm on the same g1 screen. if i take the battery out i can boot to recovery mode but my only options are alt-w and alt-s. i've tried wiping and reflashing with the same spl img and it's not resolving anything.
I have a Mytouch 3G running test 7 on my phone, and i just installed the clockworkmod rom manger. After, installed it i wanted to flash a new rom, so flashed the clockwork mod recovery, and when i tried to install the new rom from the sd card, it keeps on getting stuck on the mytouch screen, and nothing happens. How do i get into the recovery screen? thanks
First: This belongs in Q & A !!!!111
Which ROM did you flash? Maybe you had to wipe before
right now, i'm running cyanogen test-7, but when i go into the clockworkmod rom manger app and pick the flash rom from sd card, it just says it has to go to the recovery, and then my phone will reset and it would just get stuck on the mytouch screen. So, i just pull out the battery and reset the phone again, and i realized if i press the end button, it will go the rom that is already on the phone. I'm i suppose to push some buttons or something to get to the recovery screen?
No it should flash the rom you select and reboot the phone to boot the new rom without keypress needed.
maybe the wrong device was selected when downloading the recovery image? Try reinstalling clockworkmod recovery from rom manager.
Mod edit: not dev related, moved to q&a
I have the same problem.
I downloaded and installed Rom Manager from the Market and it has completely screwed up my recovery (I can't get into it at all). I tried flashing Amon's again (through Rom Manager) and it still doesn't work.
HTC G1. CM5.07 test 7 (trying to go to stable!).
Your recovery has been corrupted, you will need to flash it through fastboot.
JAguirre1231 said:
Your recovery has been corrupted, you will need to flash it through fastboot.
Click to expand...
Click to collapse
Yes thank you. I erased recovery partition in fastboot then reflashed Amon's.
Working now.
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
illmatic282 said:
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
Click to expand...
Click to collapse
Connect to your PC via USB, and from the command line issue "fastboot erase recovery" and then "fastboot flash recovery filename.img"
More on common fastboot commands here can be found on these forums, i'm not allowed to post links.
i connected my phone to my computer but nothing on my computer pops up. only the new hardware wizzard pops up. what do i do from here? im i suppose to get a adb popup? how do i set up the fast boot? i'm so confused..thanks
some one, please help..i want to be able to flash new roms in the future...thanks in advance
Can I sugges that you try this sticky thread at the top of this forum board.
It contains all you need to know on who to set up fastboot and how to use it - there are a couple of tutorials on it if you read through the thread.
CM 5.0.7 for Dream/Sapphire introduced a bug in flash_image. It causes recovery flashes to fail. It has since been fixed in the latest test of 5.0.8 I believe.
Man i have the same darn bug cant get back into recovery for nothing, and i dont have a pc to fastboot i have a non intel based mac so no adb or fastbooting, i have been doing fine for forever without adb or fastboot but is there any way around this one, i need help bad, im on HTTClay Superbadv1.3 and it has all sorts of bugs but i cant nandroid or bart or flash any rom without recovery, can someone please help!!!
Also is there another way to erase the recovery partition?
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!
I've been searching and I should add that my bootloader is not unlocked
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !
1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons
Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.
Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.
I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!
Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??
well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"
Do you have Busybox installed?
Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?
Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.
Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]