Im the owner of an old Iconia A500 Tablet.
I tryed to root it with the after ota Tool and IT says i can install root with Recovery now. But the Problem ist the Recovery doesnt Work. I get a dead Android in Recovery (Volume - + Power).
I tryed to install a custom Recovery via afterota but i had No luck.
I installed the OS via the Recovery which worked so i dont understand why i cant access the Menü in Recovery and why i cant install root.
Maybe Someone can help... I Hope
Maybe you can Guide me thru and help me to install a fast and slim Rom for the Tab.
I would Like to use the Tab as a Wall mounted Info Panel with a calendar and maybe some smart Home Software...
I cant Tell you the exact version cause im at Work right now but ill do later. Just ASK me what you need.
Best regards
Tim
Related
Hi guys, I have one Kinpad i600, and last week try update, using
wrong rom( I get on this forum).
Now my tablet is bricked, cant update using recovery mode (I alread try put anothers rom version on SD CARD and nothing).
Cant acess for ADB too, in Windows I dont locate yet correct drivers for this tablet.
I just install Ubuntu on another PC, and try install ADB too, but no sucess on access tablet.
Someone have one idea to resolve my problem??
Sorry for bad english
You need to enter recovery mode.. i dont have a kinpad so idk how.
Once you are in recovery, you can then maybe fix it.
Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD
I have searched a lot, and i cant seem to find a resolution for this
I have a GT-I9000 with no 3 button combo, i made a jig and i can get it to enter download mode no probs, but when i plug it into the lappy, i get unrecognised device. Its not the drivers or the port, as i have other phones that load fine.
have tried all the drivers and tips that i can find, i see a few ppl have had the same issue, but i cant see any real solution
i can boot the phone into recovery with ADB
i wouldn't mind even just being able to upgrade to stock gingerbread.
But i'm not sure what i can flash as "update.zip" in stock 3e recovery with Froyo base.
is there anyway i can upgrade fw using stock 3e recovery?
any help would be appreciated
Regards Tony
Can't you connect to kies for flashing new firmware?
absolutely, and all the usb drivers work fine while booted up, but kies reboots the phone into Download mode to install firmware.
and when in download mode, device not recognised
Y don't u try a diff laptop or pc...
U can try this for rooting :
z4root
Or
Since u can enter 3e u can try this update.zip method
And then u can try this ater u root...
Mobile Odin... but i dont knw whether its compatible with froyo... if its compatible u can flash any stock gb package...
If anything goes wrng i ll try my best to help...
z4root worked fine, and installed superuser
but mobile odin comes up and says "unable to find superuser package" ?
Try installing busybox then... ie rooting, then busybox, then odin...
all good, updated su to the latest version in market and now Mobile Odin is working .
one question, seeing as though i have unrecognised device when in download mode, if i flash stock jvn coming from Froyo, and it hangs or fails.
im pretty much fried arent i?
See whatever package u ve... just extract it and check that it shud be a 3 package one ie pda modem and csc... and the pda file shud ve boot.bin and sbl.bin... or else u ll be stuck in a bootloop as gingerbread has diff bootloaders... and use the necessary pit file also...
If ur package doesnt ve all this then download a diff one with these... jvt and jvs ve these...
If u go sme pages back in development section u ll find custom roms for froyo as well... we can evn hope that flashing that via recovery might fix ur 3 button issue...
And even one mre thing which i forgot to ask was that is ur phone sim locked ???
And yes u wud be pretty much fried if this doesnt do the job as even ur phone wasnt responding to jig...
We can just hope this wrks...
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.
[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom
Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed
Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:
Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*