Help with ADB... - Android Q&A, Help & Troubleshooting

I'm totally new to using ADB and am mucking my way through as best I can. To experiment, I'm trying to resurrect an old TMO Alcatel One Touch Pixi 7. I'm reasonably sure that I've found the right boot, recovery and system images and the machine is recognized in ADB but when I try to sideload them, I get a signature verification error. So, I don't know if I need to figure a way to get the signature right (I haven't a clue as to how to do that) or make a .zip that I can load onto the SD card and flash via the stock recovery.
If I'm going to flash via the stock recovery and a .zip, I have no idea how to make a .zip for the SD card. I know that if I use that method, I can turn off signature verification.
Just a note - I am totally new to anything Android development. I have rooted every phone I've ever owned but most are Samsungs and the Pixi died as a result of trying to root it. I managed to resurrect an old Samsung Tab S2 by flashing the firmware via Odin but this is my first foray into ADB or fastboot. This is my long-winded way of saying I don't actually speak the language and have done all my previous work building off the efforts of others. I am, for all intents, talent-less in this regard but trying to learn.
Any ideas/suggestions/indications on a path to follow?
I'm on my back for the next three weeks after surgery, so I might as well do this. No one wants to read my memoirs, that's sure!
Any help is appreciated!

Related

[Q] Rooting Galaxy Tab 10.1 I/O on 3.1 Honeycomb?

I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.

Will pay $$$ for help with TF201

So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
LivioDoubleFang said:
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
Click to expand...
Click to collapse
Not sure what recovery you have now but I suggest you go here >>
http://forum.xda-developers.com/showthread.php?t=1615990 and install twrp recovery through the fastboot method. Boot into trwp recovery. After that, download the nvflash files from here http://forum.xda-developers.com/showthread.php?t=1774352
Not saying you should use nvflash at this point but the file also contains a known good adb.exe file. Unzip the file and while in that directory press and hold the shift button while right clicking the mouse. This will bring up a menu select open command prompt here.
Put your rom into the same folder as the adb.exe then in the comand window type adb push /name of your rom.zip /sdcard/ if this doesn't work use /sdcard/media At this point you should be able to install the rom. As for the rom, a good starting point would be androwook rom since it seems to install quite easily (do not unzip). Also when you are performing commands in either fastboot or adb, it is best to copy (control c) from the webpage then in the command window right click and paste, this eliminates errors. Having the files you are flashing in the same directory of fastboot or adb eliminates the need to type pathways, this is where many people run into issues, 1 wrong letter make everything not work....
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
LivioDoubleFang said:
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
Click to expand...
Click to collapse
Most people don't have a stock backup since once you are unlocked, trying to install the ota update can make the tablet inoperable. So basically when Asus updates the software then the developers here pick up the stock rom and enhance it. This goes anywhere from the base stock rom with root up to taking the rom and customizing it with options, kernel changes and such. The only thing I will say about changing kernels is only use kernels that were developed for the particular rom or you will have trouble. Kind of like taking a Ford motor and trying to mate it to a chevy transmission.
If you do change roms, make sure you wipe cache, dalvik and do the factory reset from within twrp. When you become comfortable, I suggest looking at the NVflash thread in the dev section. This will provide you with a bit of assurance that you can recovery from most software brick situations. Read over the instructions a few times before you go a head and take some time to read through the thread so you know what could potentially go wrong. It really isn't that difficult to do but you should be well informaed before proceding. If you need anything else don't hesitate to ask
Another thing that i find helpful, keep a stock rom in your sdcard. When i semi-bricked my 201, i was able to flash the stock rom using CWM, then do a factory reset. Once back to factory, i was able to boot and start over again.

Wiped OS on HTC One X+

So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.

[Q] No Access

I have to start by telling you I am not only a Newbe I am a NO-Knowbee, a complete novice. I am an advanced computer user but smart phones make me fell stupid. So please bear that in mind when offering "how to" advice.
I bought this phone 3 weeks ago as Rooted. I think is was rooted but SuperSU will not start. I get a message that the SU Binary need to be updated. I have two choices. NORMAL which fails and the other is TWRP/CWM which does nothing either but suggests I manually reboot into recovery manually. I have no idea what to do.
Nice mess there ... maybe others have better opinion here but .. the question would be to fine out what version of android you have (aka like windows xp, 7, 8/8.1 etc) then from that point I would almost want to start over ..
Some people have differ opinions on this but my opinion is to start over and re-root the phone. Either they failed on the unlocking boot loader or something and just decided to sell it. (in windows terms they basically corrupted everything).
So the question comes down to is being able to put on custom roms? Depending circumstances you can unlock the boot loader and then install any custom rom (modified OS made for that specific phone, you cant just put anything it has to be made for this phone etc..)
Next question if you can live without going through that (different roms) and want to stick with stock (whats already on the phone) and just want root, then the my opinion would be to just redo everything then re-root it fresh.
Theres a program called Odin that you would use and you would need the stock file to which is currently on your phone and you would need to download it (the file is usually about over a GB in size) and you would need to do that. However telling you how to do that here while its simple this is something you need to read and learn about. Its just like finding tweaks and tips on windows. There's a EXCELLENT help section here and I HIGHLY recommend you read and read more and more. Its like potato chips you cant eat just one. Good luck.

Creating Recovery for Unsupported Phone

I recently rooted my phone and I would like to make a backup before I mess around with a few things. The phone I have is a Galaxy K Zoom. It's running 4.4.2 Kitkat.
My problem is that CWM and TWRP don't seem to work. CWM tells me that my phone is unsupported, and TWRP says it will backup, but when it reboots to create it, I get an error. Is there another recovery app that is available? Or am I stuck having to restore to stock if I soft brick it? I'm ok even using ADB and/or Odin to flash it back to the phone, but I just need to make a recovery to start with.
Also, I have a recovery file that I found in a rooting thread for my phone. Won't that recovery file restore to their phone's settings? How can I make my own? I'm sort of a noob at this, so sorry for asking.
Thanks in advance and I really hope I get get some direction here. I'm more than willing to read through threads, I just don't know if I'm searching for the right terms. I noticed that there have been some posts on this before and there were no replies. Hopefully I can get one!

Categories

Resources