Related
Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery
If an aftermarket launcher is your problem, use adb uninstall to get rid of it or any other apk that is causing problems.
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
JacenSolo2001 said:
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
Click to expand...
Click to collapse
in order to push files I think you need root. if you've rooted your phone, use the su command to get the # prompt, which is super user status.
ok, here's where I'm at:
Android system recovery screen, with the 4 options, reboot, reinstall packages (which can't find the zip file), and the 2 deletes. This is the only place i can use adb at from here:
I do an adb devices and get
List of devices attached
I89789fda6da recovery
So at this point, is there a way anyone knows of to get the zip file to the internal sdcard?
oh and btw: the phone is rooted
Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>
i don't think busybox is on there any longer, it just says busybox: not found
dewt said:
Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>
Click to expand...
Click to collapse
I don't get it: what wget will get? Are you saying I need a web-server on my windows laptop?
Please be more specific: update.zip sits on my D:\tmp. How wget will see it?
Example please
JacenSolo2001 said:
Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery
Click to expand...
Click to collapse
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.
alphadog00 said:
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.
Click to expand...
Click to collapse
Exactly what I was thinking. It doesn't make sense to be trying so hard to fix that when a simple one click Odin will remedy the problem.
Sent from my Captivate
Axioo PICOPAD QGN
Android OS, v2.2 Frozen Yogurt
Qualcomm MSM7227 (App: ARM11 600MHz)
This wont work on PICOPAD 9
This is a very unpopular device from Indonesia. Although it is very easy to Root using "Superoneclick". As more people got hold of this free set(via Singapore old Starhub Internet plans), more people are also starting to ask about the steps on rooting this device. I thought I should start a guide here where I've followed from different places, piece them together here.
Feel free to comment and share if there are other ways to root, flash and install custom roms or android version. More importantly over clocked kernels. (remember seeing a link at kwbr's thread)
There are similar sets "CSL Spice Mi700 DroidPad", "Viewpad 7", etc
Alternatively you could research more by heading on to Viewpad 7's thread as I found out that device is very much similar and more developers are active there. I've also tried flashing kwbr's rom and it works for me.
Well if you are going to follow this thread to root, then read on...
WARNING! You warranty is now VOID & I will not be responsible if you brick your device.
Click to expand...
Click to collapse
Sections:
1. Rooting your device (wiki)
2. Installing Clockwork recovery (wiki)
3. Setting up ADB (optional)
4. Setting up partition on SDcard to free up device main space (WIP)
1. ROOT & Busybox (comes in a package)
Use these steps to root with "SuperOneClick". (Thanks to SuperOneClick)
Download and install "SuperOneClick"
Alternatively, download older version (some say works better) 1.6.5 1.7.0
Make sure you have .NET Framework v2.0 for Windows XP(win update)
On picopad, Unmount your SD card. From settings -> sd card -> unmount
Enable USB debugging, Setting -> Applications -> Development -> tick USB Debugging
Connect picopad to Pc via usb, ignore pctools if popup.
Goto Windows Explorer, Picopad will appear as "CD-ROM", explore CD-ROM and run SETUP.exe, ignore pctools
Open "SuperOneClick"
Change the option from "psneute" to "rageagainstthecage"
Click Root.
Rooted , Superuser & Busybox installed
Mount back your SDcard if u wish and reboot your device at least twice.
Congrats! Your device is rooted!
If you are satisfy with only root and superuser access, then you can stop here.
If you would like to install(flash) Clockworkmod recovery so you can backup your device(nandroid) and flash rom/kernel/stuff easier, proceed to step 2. (Highly Recommended)
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
2. ClockworkMod Recovery 5.0.2.6
2a. Preparing to installing CWR
Download CWR 5.0.2.6 and Flash_Image
Unzip, then copy "flash_image" and "cwm5026.img" to the root of your sdcard. (if you don't know how.. take your SDcard out and use a card reader)
Power on the device and install a terminal app so you could type commands in, try Android Terminal or Terminal Emulator
Once installed, open the app and start typing:
Gain superuser access type
su (once in superuser, you will see "#")
Click to expand...
Click to collapse
copy flash_image to system/bin
cp /sdcard/flash_image /system/bin
Click to expand...
Click to collapse
Install the flash_image
chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
Backup your original Recovery
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
Click to expand...
Click to collapse
And if you ever want to restore back for warranty issues
flash_image recovery /sdcard/orirecovery.img
Click to expand...
Click to collapse
2b installing ClockworkMod Recovery 5.0.2.6
The previous ver 2XXX is pretty outdated, thanks to mb-14 for sharing 5026.
Now you are ready to flash ClockworkMod Recovery
Assuming the file name that you download from CWR is "cwm5026.img" Type
flash_image recovery /sdcard/cwm5026.img
Click to expand...
Click to collapse
Done!
Now to run Clockwork Recovery:
First, turn off your device.
Now, hold down both volume button and press the power button at the same time, when you see recover on the corner of the screen, you can let go as you will boot up in Clockworkmod Recovery.
How to use 5.0.2.6 CWR?
Use the device vol+ and [/b]vol- to move up and down or the soft keys menu for "down", home for "up"
Select options by pressing the power button or , use the soft keys search for "enter"
back is for "back".
When you load into CWR, you could do many stuff, some simple info on the main options,
Wiping data is resetting your device to factory default, but CWR remains as long as you do not flash a stock recovery or a rom with a different recovery inside.
You could do stuff like formatting and partitioning SDcard to prepare for Apps to be install in SDcard to save space in device. Other than that, you could do a Backup for your entire device which is also known as nandroid backup, but it doesn't backup the bootloader and radio, so take note if you are going to flash custom radio or bootloader.
If you have a backup, you could restore back to that backup, this is good if you accidentally flash something bad or dislike a rom
Fixing permission is good if you always have FC.
You can mount SDcard to your pc from here and manage files with from your PC.
You could use ADB to push / pull files in and out of your device from PC.
you could install other roms, kernel and files using the "install zip" option.
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
3. Installing ADB on your windows
Download and install Latest JAVA SE Development kit "JDK" and Android SDK.
Follow the steps here on installing ADB, Android Debug Bridge.
3a. SET PATH for ADB: Check if you had set the path to sdk platform tools folder, this is to run adb command from any path. Steps for Windows XP:
Right-click ‘My Computer’ and click ‘Properties’.
In the ‘System Properties’ window, click the ‘Environment Variables’ button on the ‘Advanced’ tab.
Find ‘Path’ in the ‘System variables’ section and double-click it to edit it.
Make sure NOT to delete the existing entry in ‘Variable value’.
Just add the following string to the end of it, including the semi-colons:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools;C:\Program Files\Android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
Start ADB shell to command picopad from your pc:
Make sure Picopad is connected to pc via USB and sdcard is mounted.
From PC, Goto command prompt (Start -> Run type "CMD")
Type "ADB devices" from command prompt ( to see if path is set and picopad is connected, you should see 1 device attached, not more, not less)
C:\Documents and Settings\tish>adb devices
List of devices attached
FM88888888888 device
Click to expand...
Click to collapse
Troubleshooting:
If you can't get the adb command to work, probably you didn't set the path correctly, refer back to SET PATH or go to your adb actual folder to type the command which should be here C:\android-sdk-windows\platform-tools\
3b. Using ADB
At recovery or booted up device, on Pc Type:
adb shell (you will see "$")
Click to expand...
Click to collapse
now access superuser type
su (allow superuser access from Picopad and you will see "#")
Click to expand...
Click to collapse
Here you can copy files using (push/pull), I recommend you google for ADB commands to have a better understanding.
4. More sections to come eg: The space problem on the device, so alternative is partitioning sdcard to install apps as to free up space in device........
You could buy me a beer if you really appreciate my work here.
Updates from Fri the 21th April 2012
Reorganizing error section
Adding missed out steps here and there
Placing direct link for faster downloads
Added 2 older ver. SuperOneclick which works better
Removed CWR 2.5.1.2 details since it's outdated.
Added some details on 5.0.2.6 CWR
Updates from Fri the 13th Jan 2012
Added CWM 5.0.2.6 and soft keys steps.
Added possibility to explore Viewpad 7's dev forum.
Included some wiki info on root and CWR(Clockworkmod Recover)
Added troubleshoot for Set path to android sdk adb folder.
Included ADB set and using step
I first rooted my Picopad using guides from hucqim80, however they are not meant for Picopad and I've gather the info and posted them here.
Original recovery image provided by jax79sg here
This is to recover original recovery and replace clockworkmod recover.
This step is done because you need to send your set for warranty repair probably.
Remember to do a factory reset first before replace with original recover.
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
I will upload mine somewhere after i try your steps above.
sure, thanks
axioo picopad.
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
did u go to cd-rom folder and execute setup.exe before u click superoneclick?
No , I did not run the setup.exe from the cdrom drive cos when i plugin the device it automatically ask me to do the PC syncing. Actually i tried that before but that din work either.
I ran both PC running win7 and winXP, both also stuck at Running psneuter ...
Hi,
I ran into this error which puzzles me greatly.
# flash_image recovery /sdcard/cwrecovery.img
flash_image recovery /sdcard/cwrecovery.img
flash_image: permission denied
Do you know how to resolve this?
Thanks in advance.
Warmest Regards
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
same with me....anybody can give another tips ?
try to turn on picopad usb first. then try to ru he setup in picopad identified as " cd-rom" try again
Sent via Picopad
is there any custom ROM compatible for this device ?
help
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
can this Stock ROM modified for support with App2sd by Trkton ?
Vuska said:
can this Stock ROM modified for support with App2sd by Trkton ?
Click to expand...
Click to collapse
It supports without any modification in the first place.
Roms, probably the MI700's custom rom will work, get to hucqim80's signature, the link is there.
nhasir said:
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
Click to expand...
Click to collapse
probably ur file is not in that directory for this error message to appear.
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
Okay, i know your problem... just change the option in superoneclick from psneuter to rageagainstthecage... and then root it...
when the superoneclick start to not responding, just re root it using the same method....
then to enable your superuser, install z4root to your device
I managed to root the picopad and flashed as stated.
When i boot up pressing both power and vol button, i was brought into this FTM mode. And from there i can't do anything...... the screen looks as follows.
Hmm....the cwrecovery didn't get flashed?
SWVer=3.240
MODEL: FM6-0001
HWVer:106
Power on with pressing VOLUME_DOWN keys to leave Auto FTM.
[Resolved]
Try holding both up and down volume buttons instead of just one of them
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
jax79sg said:
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
Click to expand...
Click to collapse
Im still using my picopad.
Thanks!
Sent from my Nexus S using XDA App
can anyone help me with original backup for the splash and welcome screen axioo pico pad?
my pico pad splash and welcome screen change to viewsonic because i install viewpad 7 ROM in to my pico pad.....
somebody....help me please !!!
thankyou
Hi all.
Everyone here on our forum wants to help devs by testing different stuff but devs wants testers to send debug info to them so they can resolve bugs. Notifying bugs without logcats is useless and some users don't know how to collect these debug data.
To collect debug info there is a tool named ADB (Android Debugging Bridge). we r very small community and there are not plenty of sgr users around here so we have to worry about knowledgeable testers. so i m making this basic instructional guide to ADB. about how to set up ADB on windows and some basic usage.
Setting up ADB on windows.
Know this first.
> ADB requires usb drivers. So first of all install kies so that ur pc detects ur phone and ADB can recognise ur phone.
> Android is linux based and in linux commands are case sensitive so while typing these command use propare case otherwise commands won't execute.
> Windows uses back slash [\] and linux uses forward slash [/] so while typing file locations. For location of file in ur pc use back slash and for files in ur phone/sd card use forward slash.
there are two ways to setup adb on ur windows pc.
1 > download the android sdk, it includes the adb
u can download latest android sdk from HERE.
2 > only download adb package, no need of downloading the whole sdk.
look at the end of post to find the zip file of adb package.
now after downloading:
if u have downloaded sdk read this:
> after downloading sdk, extract it to ur desired location.
> after extracting, open that folder and goto "platform-tools" folder.
> now hold the shift key and hit right click in that directory
> click "open command window here"
> u will see command promp, type "adb" in command prompt. if adb executes means u have successfully setup adb on ur windows.
if u r using without sdk:
> just extract the package
> hold shift key, hit right click and choose "open command prompt here"
> type "abd" in command prompt and check if adb executes.
now as we have successfully setup adb lets begin to some basic commands.
first of all connect ur phone using usb cable. make sure u have checked usb debugging in settings>applications>development>check usb debugging.
now open adb as mentioned above and type
Code:
adb devices
u should see
Code:
list of attached devices
xyz device
xyz will be name of ur device, as default it will be some number.
Basic usefull ADB commands
1.
Code:
adb pull
this command can be used copy files from ur device to ur pc.
for eg.
Code:
adb pull /system/app/Camera.apk
this will copy the camera app to the directory where adb is extracted.
if u know the path u can copy anything using this command.
2.
Code:
adb push
this command can be used to push files to ur phone.
type the command, drag and drop the file in command prompt and than type location where u want to push that file and hit enter.
for eg, if i want to push image named android.jpg stored in my C drive.
Code:
adb push C:\android.jpg /sdcard/
this will push that image to sdcard.
sometimes we have to push some packages in specified folders. just type the location after file name.
for eg
Code:
abd push C:\sanim.zip /system/media
3.
Code:
adb install
with help of this command we can install apps to our phone dorectly from pc.
for eg. type "adb install" than leave one space with mouse choose apk file of app u want to install and drag and drop it in command prompt. path of that app will be displayed in command prompt. like this.
Code:
adb install C:\adb\Camera.apk
by executing this command u can install the app u have dragged and dropped in command prompt.
As i have written for windows but these commands can be used on ADB on linux/MacOS as well but i have only mentioned the set-up guide for windows only.
Credits/Source.
http://developer.android.com/tools/help/index.html
Getting Debug Infos (Logcats)
1. logcat
logcat is a report from android logging system which runs in background from the moment u boot ur phone. and it haves all the info what went wrong with system.
generally we can see logcat by typing
Code:
adb logcat
but that will show the constant data flow so better save it as file so can be sent to dev or u can study it later.
Code:
adb logcat > log.txt
this will store the logcat to directory of adb and collect log in text file.
2. bugreport
Code:
adb bugreport
bug report prints dumpsys, dumpstate, and logcat data to the screen. which can be used for bug reporting.
3. Java Debug Wire Protocol
Code:
adb jdwp
this command prints the list of available JDWP processes on connected device in command prompt.
Logcats On Mobileu can directly generate logcat on ur mobile using Terminal Emulator app, there are many terminal apps in market. CM comes with pre-loaded Terminal Emulator.
some terminal apps:
Android Terminal
Terminal Emulator
RomToolbox
u will need root access to generate logs
open terminal app, u will see following screen
Code:
$ export PATH=/data/local/bin:$PATH
$
now type su and hit enter.
allow super user permissions.
now to get a logcat type following command.
Code:
logcat > /mnt/sdcard/logcat.txt
this will generate text file named logcat.txt on root of ur sdcard which is containing logcat.
to get DMESG (Kernel Debug)
open terminal and type following command
Code:
su
dmesg > /mnt/sdcard/dmesg.txt
this will generate text file named dmesg.txt on root of ur sdcard which is containing kernel debug log.
Kernel Debugging.
we can use adb to debug kernel issues.
Code:
adb shell
dmesg
this will generate a log which is very helpful to resolve kernel issues, we just have to send this log to dev, he will look after it.
sometimes after flashing kernel we go into bootloop in that cases generate logcat using this commands and send to dev it will be very helpfull for dev to know and resolve reason causing bootloop.
Code:
adb shell
cat /proc/last_kmsg > /sdcard/last_kmsg
this command should be executed immediately on reboot otherwise it will be over written by new kernel message. the file will be stored on root of ur sdcard named last_kmsg. send this file to kernel dev it will help him great to resolve the problem.
Read this if u dont know how to get files from ur sdcard even if ur phone is not booting and stuck at bootloop.
u must have CWM to do this.
>boot ur phone in recovery mode (by holding VOL UP and HOME key together on boot)
>goto "Mounts and Storage"
>Select "Mount USB Storage" and plug in your data cable.
>Now u can access ur sdcard on ur pc, after ur work is done click "Unmount"
Hi,
Just a noob question... if my phone is stuck in a bootloop, is there anyway for me to get a logcat without flashing a new rom???
Sent from my GT-I9103 using xda app-developers app
JoJo2012 said:
Hi,
Just a noob question... if my phone is stuck in a bootloop, is there anyway for me to get a logcat without flashing a new rom???
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
If you have enabled USB Debugging , yes
"I have to go. It's just....they really need me." - Sora
Re: Toggle mobile data on and off via adb
Does anybody know how to toggle mobile data on and off via ADB?? IM WILLING TO PAY FOR THIS INFO lol I NEED IT THAT BAD!! PM ME PLEEEASE!!!!!
12manytimes said:
Does anybody know how to toggle mobile data on and off via ADB?? IM WILLING TO PAY FOR THIS INFO lol I NEED IT THAT BAD!! PM ME PLEEEASE!!!!!
Click to expand...
Click to collapse
'adb shell su -c "svc data disable"' and 'adb shell su -c "svc data enable"'. You must be rooted.
Sent from my GT-I9103 with CM10
Adam77Root said:
'adb shell su -c "svc data disable"' and 'adb shell su -c "svc data enable"'. You must be rooted.
Sent from my GT-I9103 with CM10
Click to expand...
Click to collapse
Thanks alot, i just sent you a PM but it shows that i didn't send anything, so if you didn't get the message please send me one cuz id like to buy you a beer!
I wish i could hit your thanks button a million times right now lol
Hello I am trying to create a batch file that has an infinite loop and was wondering if there are any adb commands that can do this.
I am also looking for an adb command that waits x amount of seconds before performing the next command.?
Any help would be greatly appreciated
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52
Thank you kindly for taking the time to respond and also help.
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6
Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa
360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.
360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied
Hey folks!
I'm following this guide. From the command lines on Updating the platform-tools, I get an error "please consider trying to update again without a package filter"
Code:
android.bat update sdk -u -t platform-tools,tools
Downloaded the latest SDK and drivers. after writing down recovery.img, system.img and boot.img, I'm unable to update via sideloading.
Code:
adb sideload update.zip
The recovery screen turns out "You need adb 1.0.32 or newer to sideload to this device." I've checked out the SDK and confirmed the "Android SDK Tools (24.0.2)" and "Android SDK Platform-tools (21)" have been updated, which is possibly the ADB and fastboot etc.Now what more does it require to get ADB updated.
I've already updated the platform tools, sdk tools from the package manager. Regarding the PATH variable, Please shed some light though. I'm no experianced under LINUX or it's distro's nor have much knowledge in CMD terminal either. I've located the (cd) path to where the android.bat is installed for the 1st command line operation below.
Code:
android.bat update sdk -u -t platform-tools,tools
How come the 1st update platform-tools command went out wrong? All command line operations/downloading and writing down under the fastboot menu went out smoothly, except this sideloading.
Thanks.
:angel:
cloutz90 said:
to show the adb version use
Code:
adb version
it should be 1.0.32 or newer (see image attached)
Click to expand...
Click to collapse
I checked with the exact command line also, it's the same 1.0.31! Also the package manager shows out I'm at the latest platform and SDK tools.
Sigh of relief!
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:
CODENEX said:
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:
Click to expand...
Click to collapse
Having the same issue. How exactly did you "update the ADB version to the directory"
ADB issue
SantinoInc said:
Having the same issue. How exactly did you "update the ADB version to the directory"
Click to expand...
Click to collapse
about this ADB version issue, i have a different phone, but was facing almost same sort of problem.
I think he might have referred to this thread: http://forum.xda-developers.com/showthread.php?t=2317790;)