I am really confused with all these threads and everyone's own abbreviations... I would appreciate some insite if possible ... yeah, call me stupid
Okay, so I previously installed gingerblur on 1.86... working great.
I unlocked the phone (I guess) this morning, cause now after I finished, I get the wonderful "Unlocked" note on my boot screen.
Anyways, my question now is... what do I need to do next to get 2.3.3 on this bad boy? Is the next step to root it again? Or do I go straight into the flashing process?
I tried to use this method (I downloaded all files into my C: root), and when I run the first command it tells me "Waiting for phone"
It just sits there after that.... Is it a really long process? I waited about 5 minutes and still no go.
Can someone please help me understand in a real easy flat language ?
Thank you so much
This is the method I was referring too...
http://forum.xda-developers.com/showthread.php?t=1139715
I can help
Make sure you have all your drivers installed, if you had them before, make sure you are using the same usb port.
Also make sure your phone is on usb debugging.
You can also run afterupdate bat file. (not needed)
Anyway extract the folder to your c drive.
open up cdm and you will see this
C:\Users\Your Name>
Now this is what you will type , your screen should look just like mine as long as you havent changed names of anything.
C:\Users\Your Name>cd C:\android-sdk-windows\tools
Then type this
cd C:\moto-fastboot
moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
moto-fastboot flash system atrix-2.3.4-hktw-system.img
moto-fastboot -w
moto-fastboot reboot.
I know you installed the android sdk tools but just in case watch this video
http://www.youtube.com/watch?v=y6K1XLmafPc.
hope this helps
Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
I see they are flashing custom files / ROMs on the Kindle Fire using fastboot. I believe we are limited on this due to our current bootloader state, but does anyone with experience with Fastboot know if this may be a possible working option until we can get CWM / recovery ?
I agree, can someone please try this? I've seen romified asking this question several times but no one seems to have tried it. The chances aren't great, but it's definitely worth a try.
might be as simple as "adb reboot fastboot"
and then "fastboot oem unlock" or other commands (I'm not too familiar with them myself)
This harks back to the (not so long ago) days of flashing via fastboot on my HTC Magic, which have since passed since I move onto a SGS II.
Edit: Oops it wasn't romified who asked this previously. Can't remember who it was. But either way, that's not really important.
I have not asked about fastboot yet as I just though of it and did some quick research. I am comfortable hacking roms and decompiling files and what not, but bootloaders and hacking recovery is new to me (for now anyway) As soon as I get to where I can I will dig into it further but if someone knows it isn't going to happen with this bootloader, no need in wasting time on it. It could open the door for other possibilities as well. I tried to get fastboot to recognize my NT but no luck. It was just a quick try though.
Did you manage to get the NT to get into fastboot mode though? Probably using the adb reboot fastboot or adb reboot download command (unless we find the hard button shortcut to it)?
I don't have the Nook Touch yet, but will probably be getting one to play with soon (the gf has her eyes on one). Either way, the more capability unlocked, the better.
If you can get the device into fastboot, it's a matter of looking carefully at the USB device tree and seeing that you have a fastboot device listed, then digging through the strings until you find a string you can use to communicate with the device.
If Fastboot isn't included with the NT, it is available with a number of other software packages.
I know it's part of one of the Lenovo LeTools packages, for instance, which is available for download for Windows hosts. If you get the copy from LeTools, be aware that it will install (or try to) the LeTools.apk that's bundled with it from your computer to any bloody Android device that's attached, not just to Lenovo devices. So you may want to delete LeTools.apk after installing and before connecting your NT.
Or you might want to try leaving it there as an experiment. The apk does some interesting things, one of which is make your device discoverable via wifi, at least if it's a Lenovo branded device.
The release of LeTools I just confirmed fastboot for is available at http://consumersupport.lenovo.com/us/en/DriversDownloads/drivers_show_5004.html release IN12STW151WW5.exe.
You don't need to install everything to get fastboot - you can unzip the installer a couple of times to get to the install.msi file for just the tools.
Im faily new to the android world. please forgive me of any stupid questions that i may ask.
I was trying to reinstall a new version of maximus 7 on my htc one .
i had the CM 10 installed and was having wifi issues. read that i should clear data and what not and instead of doing a factory reset....i did a format...
now i have no rom on the phone and cant figure out how to do this.
ill upload a video on what i currently have going on...
when i plug it in to the computer...i head the noise from the computer saying that it connected..but nothing popped up.
please help.
heres the youtube video of whats going on with the phone. take a look and suggest any fixes . thanks.
youtube.com/watch?v=NCSJPpLuQiE
adb sideload. you should search this thread there are many that will help you
i searched what i could. didnt find much because im not familiar with terms much.
andrey64 said:
i searched what i could. didnt find much because im not familiar with terms much.
Click to expand...
Click to collapse
you should download all in one toolkit and use the sideload feature. read the on screen directions as you go through the process and you should have no problems
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery
Phone bricked stuck on Android screen,access to adb & fastboot logs provided [Solved]
Hello,
I recently messed up my phone. Long story short, I snatched an OTA, modified it and tried to force it on my phone. The vanilla OTA always failed in the check process because I modified some /system files on my phone. In result of that, a couple of files has been wrongly patched ( /system/app/OpenWnn/OpenWnn.apk ; /system/bin/debuggerd ; /system/bin/install-recovery.sh ; /system/priv-app/ApeCloudFileManager/ApeCloudFileManager.apk ; and maybe others indirectly ). I can provide more informations about my slip up if you wish.
Since then when I start my phone I'm stuck at the "Wiko, powered by Android" screen. I can access the stock recovery menu, and the factory mode. I also have access to my phone throught adb, adbd, and fastboot.
My phone is a Wiko Rainbow Lite 4G ( http://world.wikomobile.com/m745-rainbow-lite-4g ), the actual manfacturer is Tinno so the phone is probably sold under different names around the world, Wiko being only a "middle-man".
With that said, I can't flash the ROM using the utility given to me by Wiko. They do not provide "stock rom" with scatter file, but instead use their own software, a sole .exe file ready-to-use, you hook your phone to your pc, restart the phone by pressing random combination of buttons, and voila. However, I managed to extract the system.img, boot.img, etc files from the .exe . So I figured out I could try to use "fastboot flash system system.img" command to restore whatever files are messed up. Might as well not touch /recovery and /boot because I can access the recovery the phone seems to boot correctly ( from what I understand /boot is just a bootloader, so me being a pc-guy I wouldn't see the point of reinstalling GRUB if windows was missing a dll or something like that ) .
But the phone is locked .... Here's the "fastboot oem device-info" result
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
And I when I try to "fastboot oem unblock" :
Code:
FAILED (remote: oem unlock is not allowed)
So yeah .... I'm stuck there. If anyone got an idea, even a vague one of what I could try next to unbrick my phone that would be very kind of you. There's no wrong answers. So please if you got a couple minutes to spare (you already made it through my laïus which is already something ) I would be very grateful.
I'm thinking about extracting files from system.img and copy them on my /system partitions throught adbd with a script .... But I'm not sure if that would help or make it worse.
If you need informations here's the logcat I got under "factory mode" ; part1 : http://pastebin.com/nx7BC8K5 , part2 : http://pastebin.com/eU94B9VE
the pstree (because come on, if a phone can launch all of that, certainly there's something we can do to repair it) : http://pastebin.com/ZWd6vC9q
dmesg : http://pastebin.com/RYfbF0ub
prop : http://pastebin.com/k6T4bYnu
cpuinfo : http://pastebin.com/a6eMQTmd
PS : Yes I'm still a noob when it comes to Android, but please if you have any questions, need more informations, ask and I shall provide.
PPS : @moderators, I apologize if I posted in the wrong section, please redirect me
Since you extracted them, they now have a different signature and can therefore not be flashed onto the device because your bootloader only allows ROMs with their signature to be flashed successfully. Also, to clear things out, boot == kernel, boot =/ bootloader. Also, why exactly can't you flash it using their provided tools? If you are going to flash stock ROM you might as well reflash recovery and boot.
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Aramir said:
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Click to expand...
Click to collapse
YaY, you can now put [SOLVED] in the title to help other in the same issue you had!
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?