when i try to boot insecure.img it says cannot load "insecure.img" : no error
placed insecure.img in the root path (where i installed adb C:\Android)
but my device is detected by cmd "fastboot devices"
also installe HTCSync 3.0.0.007
also in Windows device manager i can see "my htc"
whats wrong?
anyone can help me
my device is "unlocked" and s-off
if i remember correctly - all the htc sync stuff should be turned off completely (through the task manager)
look here:
http://forum.xda-developers.com/showthread.php?t=1416896
guru_shastri said:
if i remember correctly - all the htc sync stuff should be turned off completely (through the task manager)
look here:
http://forum.xda-developers.com/showthread.php?t=1416896
Click to expand...
Click to collapse
htc sync is turned off bytheway cant connect tablet via sync(htcsync can not find device is problem?)
but by fastboot devices cmd is listed
and in widows 7 device manager
still didnt load insecure.img
Iv installed new htcsync correctly find my Device then i turned off htcsync pc antyvirus windows firewall
and try to root it reboot in bootloader but it still cant load insecure.img(is in root folder where adb rooted and added in "invironment var." path C:\Android)
I have :
1. adb&fastboot (11MB) extracted from sdk(downloaded work good & root in C:\Android)
2. JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img(renamed insecure.img and copy to C:\Android )
3. DooMLoRD_v2_ROOT-busybox-su
4. htc driver (find in fastbootdevices cmd and htcsync)
5. usb debbug mode
is that enough for rooting?
help please
did u make sure all the adb processes in the background are closed?
guru_shastri said:
did u make sure all the adb processes in the background are closed?
Click to expand...
Click to collapse
thanks for replying
how can i be sure is not running in background by taskmanager?
usually i use adb once and fresh to avoid interfering
i dont think thats problem bytheway i test again
can device b s-0ff without rooting?
in my device is so! (s-off unlocked but not rooted)
another Q can use wifixmanager to fix wifi problem when using another SIMprovider(not AT&T sim)
i'm having hard time figuring out the problem. you can't get root access?
can you post a picture of what happens when you try?(printscreen)
as for the s-off, i'v heard of one other device that was shipped s-off from HTC, but that's it. u might be the second one.
guru_shastri said:
i'm having hard time figuring out the problem. you can't get root access?
can you post a picture of what happens when you try?(printscreen)
as for the s-off, i'v heard of one other device that was shipped s-off from HTC, but that's it. u might be the second one.
Click to expand...
Click to collapse
i didnt buy it directly from origin shop ,seller unlocked it but i dont know he s-off it or not
no need to screen shot its simple what happennig
just :
Run \ cmd \ adb reboot bootloader(device rebooted in white screen above "unlocked" in secound line "s-off")
\ fastboot devices(devices is listed successfully) \ fastboot boot filename.img
and it says
" cannot load "insecure.img" : no error "
when try using titanum or ram manager it say device not rooted and cant access root directory in file explorer
just it, and more try will not successfull
i try a fresh adb (sure no adb running in background) as u said but no ghange
maybe any change by seller caused problem?
Try fastboot boot insecure.img
The filename should be same as what the insecure kernel's name is. So putting filename.img might be the problem. They should correspond.
Sent from my HTC One using xda premium
kailashpchhabria said:
Try fastboot boot insecure.img
The filename should be same as what the insecure kernel's name is. So putting filename.img might be the problem. They should correspond.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I know exactly did that :
as i said in earlier post
JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img(renamed insecure.img and copy to C:\Android )
(drive c is primary drive that Win7 is intstalled in)
but still it say:
" cannot load "insecure.img" : no error "
its seems no one can haelp me:crying:
maybe the file is corrupt?
try this:
https://dl.dropboxusercontent.com/u...MLoRD-insecure-kernel-autoroot-test2-boot.img
also, you need to search other devices forums. this forum is pretty dead, and i'm pretty sure an issue like that occurred elsewhere as well
guru_shastri said:
maybe the file is corrupt?
try this:
https://dl.dropboxusercontent.com/u...MLoRD-insecure-kernel-autoroot-test2-boot.img
also, you need to search other devices forums. this forum is pretty dead, and i'm pretty sure an issue like that occurred elsewhere as well
Click to expand...
Click to collapse
thanks for uploading file
i test new insecure but same problem:
" cannot load "insecure.img" : no error "
Please Help
mamalypro said:
thanks for uploading file
i test new insecure but same problem:
" cannot load "insecure.img" : no error "
Click to expand...
Click to collapse
Please l'm new member here I want to root my jetstream but i didn't find the files any where all links are currupted so could you please please please upload the files for me insecure kernel and root toolkit thank you very much
heres what u want threre is two link in middle of page
http://forum.xda-developers.com/showthread.php?t=1416145&page=6
DooMLoRD_v2_ROOT-busybox-su.zip - [Click for QR Code] : http://forum.xda-developers.com/attachment.php?attachmentid=901243&d=1329199186
JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img : http://forum.xda-developers.com/attachment.php?attachmentid=901244&d=1329199186
downoad and enjoy!
and say what happend
Related
Pantech crossover how to root.
1. install Android sdk and update.
2. enable usb debuging on your phone.
3. Download and install the pc suite to get the adb driver for the crossover.
http://www.pantechusa.com/support/crossover_p8000
4. download and extract superoneclick http://forum.xda-developers.com/showthread.php?t=803682
5. make sure that adb can see your device. From a command prompt change directory to the place that you installed the android sdk android-sdk\platform-tools and run "adb devices" you should see your device connected.
6. run superoneclick.exe make sure that you select GingerBreak from the exploit menu
7. donate me.
I am running kernel version 2.6.32.9
Bump. I figured out how to root the crossover.
josefcrist said:
Bump. I figured out how to root the crossover.
Click to expand...
Click to collapse
it gets stuck on step #6
any advice?
Well are you getting an error or what is going on?
same here. it is stuck at 6 ...no errors but it stays forever
eeter said:
same here. it is stuck at 6 ...no errors but it stays forever
Click to expand...
Click to collapse
Did you make sure that you turned on usb debugging and adb can see your phone?
usb debuging is on
How to make sure adb can see the phone?
can explain more how to:
....From a command prompt change directory to the place that you installed the android sdk android-sdk\platform-tools and run "adb devices" you should see your device connected.
checked the adb devices and device is connected. still it is freezing at step 6
Did you make sure and select gingerbreak from the exploit menu?
Worked For Me
I followed the instructions to a T and it worked for me. Thanks a lot josefcrist.
android_noobie said:
I followed the instructions to a T and it worked for me. Thanks a lot josefcrist.
Click to expand...
Click to collapse
Any time.
awesome, thanks !
its keeps not responding and freezes after i click root "adb is seeing my device "
nowseewhatudid said:
its keeps not responding and freezes after i click root "adb is seeing my device "
Click to expand...
Click to collapse
Did you make sure and select gingerbreak?
sorry josefchrist i pulled a stupid my fault thanks for the help
So has anyone gotten this to work yet?
ok so i followed the instructions, i selected gingerbreak, my pantech crossover is still at 2.2.1, adb can see my device, my sd card is unmounted and superoneclick, becomes un responsive at step 7: waiting for device... i also get a little thingy that caught my attention that says "mount:you must be root" any suggestions?
nowseewhatudid said:
sorry josefchrist i pulled a stupid my fault thanks for the help
Click to expand...
Click to collapse
Hey what was the stupid? I may be doing the same thing. If not, I can't get this to work. It just dies at step #5, no error code, SOC freezes, and I have to task kill it. I have no AV enabled. Here's my setup:
- running win 7 Pro x64
- pantech drivers installed
- development is enabled
- adb can see device
- SOC set to gingerbreak
- there is no mem card mounted or even in the device (it gets further if there is... step 7 and dies... maybe file system is inaccessible?)
What am I missing?
I would love to hear if anyone bricked their crossover..I want to root my wife's crossover, but if I bricked it I would NEVER hear the end of it!
llspragulus said:
Hey what was the stupid? I may be doing the same thing. If not, I can't get this to work. It just dies at step #5, no error code, SOC freezes, and I have to task kill it. I have no AV enabled. Here's my setup:
- running win 7 Pro x64
- pantech drivers installed
- development is enabled
- adb can see device
- SOC set to gingerbreak
- there is no mem card mounted or even in the device (it gets further if there is... step 7 and dies... maybe file system is inaccessible?)
What am I missing?
Click to expand...
Click to collapse
im in the same boat as you dude........... only im using windows 7 ultimate X84 (i think thats the number)
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
i have noticed an error message that comes up on the side thingy, it says "mount: are you root?" and ive come to the conclusion that its having a problem gaining root access to the phone... thats all.....
All Further updates will be handled in this other thread
Pre Req:
1) Make sure to install Pantech PC Suite as it will install the correct drivers you WILL need
2) Install ADB and Fastboot
How to gain Root
jcase said:
and here is root, you need fastboot and adb
androidpolice.com/2012/04/09/pantech-burst-rooted-and-the-process-is-stupid-easy/
IOMonster saved the day here, without him you would have to wipe your phone and install modified leaked firmware to get root.
Very glad we decided to not release the initial root, sorry
If IOMonster wants to explain he can, I would prefer not to however.
Details
goo.im/devs/jcase/prestoroot.img
adb reboot bootloader
fastboot boot prestoroot.img
once phone boots, reboot it again, install superuser from the market
Click to expand...
Click to collapse
How to Install Clockwork Recovery
Originally Posted by attn1
tau.shadowchild.nl/files/cwm-5.0.2.7-presto.img.zip
unzip
adb reboot bootloader
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
Click to expand...
Click to collapse
Press Volume Down and Power when booting to get into recovery
I have no come up with any of this information. I just gathered from the previous post to make it easier to search. I will try and keep this updated that way we can have a quick reference post at the beginning of the thread
Saved for future use
***Will have a Links section once this gets established***
Using adb with Ubuntu Linux - forum.xda-developers.com/showpost.php?p=28041279&postcount=641
Step by Step Root Guide - androidpolice.com/2012/04/09/pantech-burst-rooted-and-the-process-is-stupid-easy/
***Special Thank you goes to:***
jcase
Attn1
IOMonster
bulletproof1013
903tex
jackattack79
sandix
mr72
and everyone I didn't get *will update as we go*
from marcusmarcus
marcusmarcus said:
Here is what I did to get root on mine, maybe it will clear up things for others.
*Note, I am on 64bit Windows so folders will be different on 32bit windows.
On phone:
go to settings > Applications > Development > turn on USB Debugging
On Computer:
1-Download and install Pantech PC Suite from c724062.r62.cf2.rackcdn.com/PantechPCSuite_1.0.10.3314.exe
2-Launch Pantech PC Suite and update if it asks. When PC Suite is fully updated, plug phone into computer until device is recognized.
3-Download and install Android SDK from developer.android.com/sdk/index.html
4-Start SDK Manager and check the box next to “Android SDK Platform-tools” and install package.
5-Download prestoroot.img from dl.dropbox.com/u/9772722/XDA%20Forums/prestoroot.img and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
6-Download cwm-5.0.2.7-presto.img from tau.shadowchild.nl/files/cwm-5.0.2.7-presto.img.zip and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” as well
7-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
Run the following command
Code:
adb reboot bootloader
When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following command
Code:
fastboot boot prestoroot.img
After phone reboots itself, shut the phone down and turn it back on again.
Then run the following command
Code:
adb reboot bootloader
When the bootloader screen shows up again then type the following commands
Code:
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
8-When the phone boots up this time, download the play.google.com/store/apps/details?id=com.noshufou.android.su superuser app[/URL] from Google Play
---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------
FYI,
I've tried uot.dakra.lt UOT Kitchen couple times so far and have been ale to change the font of the device and the color of the glow for overscrolling but my time and other icons up in the status bar disappeared (the "AT&T" still shows up there though). The Backup and Restore in CWM does work nicely though to get me back to before I installed the zip from UOT Kitchen. I'll try 1 mod at a time using UOT kitchen and see which is making the icons and time disappear from my status bar.
EDIT: I did notice one issue with CWM backups. The backup I did today saved the folder name as "1970-02-22.03.14.56". Some reason the date is wrong in the file naming, should have started with "2012-04-13", right?
Click to expand...
Click to collapse
I hope this helps
For those having trouble with a missing driver I followed the below instructions and installed PDAnet (I did so while in fastboot mode so I could see the drivers install) as soon as it installed and the drivers showed installed. I went back and uninstalled pdanet (leaving the needed drivers behind)
hawkwind212 said:
I solved my problem by referencing to part II of the following page:
theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/Describe
Be sure to download two programs PDANet and USBView (which you may not really need but it's a nice little program).
It's suppose to be "stupid easy" to root PANETCH Burst, but who ever said that left out that it's not so easy if you don't have all the proper driver on your computer. Anyway, so soon after the fastboot mode is brought up, you should notice the computer is telling you a new hardware is found. This is when the burst switches from PANTECH's ADB driver to something else, and only way for the command "fastboot boot prestoroot.img" to work is to find the proper driver for the new hardware call "Android" in the device manager. Now you want to install PDANet, and as soon as the installation process begin, it'll find the driver for the device "Android." and install the driver for you. Once the driver is installed, the installation process will tried to install whole bunch other things into your phone, but I really don't think it can install them in fastboot mode, so you'll probably want to terminate the process. Now type command "fastboot devices" and you should see some kind of output telling you that it's recognize the "Android" device. Now, and only now you can follow the rest of "stupid easy" rooting instruction.
Click to expand...
Click to collapse
Spoiler Alert: Noob question.
Does this method unlocks the phone SIM also?? If not, there is a method to do it??
Thank you
tremeree said:
Spoiler Alert: Noob question.
Does this method unlocks the phone SIM also?? If not, there is a method to do it??
Thank you
Click to expand...
Click to collapse
This method doesnt but sim unlock is currently also being worked on.
Is there a Mac version of any of this software?
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
tfranzman said:
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
Click to expand...
Click to collapse
What software? Root..?
Cwm?...drivers? Carrier unlock for another provider? Pdl? I'm confused on what your asking...
Sent from my PantechP9070 using xda premium
bulletproof1013 said:
What software? Root..?
Cwm?...drivers? Carrier unlock for another provider? Pdl? I'm confused on what your asking...
Click to expand...
Click to collapse
I think tfranzman is referring to Pantech PC Suite and Android SDK. The Android SDK I believe has a Mac version but I do not think the Pantech PC Suite has a Mac version.
<QUOTE>Download software installed on PC : Click Here
Download MyPhoneExplorer Client App which software installed on Pantech Burst/ Breakout. You must find this from android market or you can read my previous post to get this : Click here
Connect your Pantech Burst/ Breakout device using your USB Cable Data
Please restart your phone and your Computer
After restarting finished, Now launch the installed MyPhoneExplorer Client app on your Pantech Burst/ Breakout and click on OK or Enable and it will connect to the PC Automatically,
Note :
If connection doesnt start or error you can choose another Sync software like Android Sync Manager WiFi.
If you are want Pantech Burst/ Breakout to connect on Mac OS X please follow my previous post : iSync for Mac OS X . I hope you are enjoy with this software.If any problem for downloading ,please contact me anytime</QUOTE>
I don't have a mac so I haven't tested this but this is what I found with google
Any news on CM7/9?? Im already rooted and im just playing around with UOT Kitchen
Let me know, thanks
No news as of yet. there have been people stating they are working on this but we haven't recieved any updates in awhile that I know of atleast. Anyone else reading this please feel free to correct me
All Further updates will be handled in this other thread
tfranzman said:
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
Click to expand...
Click to collapse
There is only Windows version of Pantech PC suite. proof
Finn81 said:
There is only Windows version of Pantech PC suite. proof
Click to expand...
Click to collapse
they were asking if any of the software we are using would work on a mac. the answer is yes depending on what software you are refering too. the pantech suite (which has been useless to me with the exception it installed the drivers for me) is windows only. I had actually gotten the drivers originally at work by using pda net. The information I gave above is what I came up with after a quick google search. I'm not sure if that or pdanet for mac would have those drivers.
and again this thread has ended. please follow the links in my Signature (Burst love for discussion or burst essentials for rooting information
I keep tring to root this phone but phone gets stuck in the fastboot mode and does nothing what can i do for this?
sounds like you don't have the fastboot driver installed. all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
kagedws6 said:
sounds like you don't have the fastboot driver installed. all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
Click to expand...
Click to collapse
Can you point me to the right place to get the fastboot driver's please
mobgod said:
Can you point me to the right place to get the fastboot driver's please
Click to expand...
Click to collapse
kagedws6 said:
all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
Click to expand...
Click to collapse
install PDAnet on your computer. it will install the drivers
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
Hi guys,
I known, this tema is often in the discursions. But unfortunately I'm not found answer for my problem. I'm finding it since yesterday lunch...
I have Desire X, I take factory reset and start with root my phone.
1) I have latest drivers for HTC sync and latest google drivers for HTC (I download it via android SDK)
2) I have latest java 32b and 64b and I have android SDK
3) USB debug is on
4) I'm registrated in htcdev.com (I tried manual by them but with result "device not found")
5) I tried root phone via Desire_X_All-In-One_Kit and WinDroid Universal HTC Toolkit
6) I turn off fastboot in settings of my phone
7) I'm trying it on win8 64b
And still I have problem with "no device found"
In cmd if I run adb devices and I got response. If I try adb reboot-bootloader phone is reboot into the bootloader. In device manager before restart phone into the bootloader I see my phone. It's OK but after reboot into the boadloader my phone missing. I don't known if I'm stupid or what but in all tutorials in the internet is that after reboot phone into the bootloader the phone is still visible and I can run fastboot oem get_identifier_token . But for me it is not working. Where I'm doing mistake? Please help me. Thank you.
Edit: I bought my phone by T-mobile. Can be problem there? I mean any strange version of android by T-mobile? Can I reinstal OS for clear Android for htc desire x? thx
dinamit_1 said:
Hi guys,
I known, this tema is often in the discursions. But unfortunately I'm not found answer for my problem. I'm finding it since yesterday lunch...
I have Desire X, I take factory reset and start with root my phone.
1) I have latest drivers for HTC sync and latest google drivers for HTC (I download it via android SDK)
2) I have latest java 32b and 64b and I have android SDK
3) USB debug is on
4) I'm registrated in htcdev.com (I tried manual by them but with result "device not found")
5) I tried root phone via Desire_X_All-In-One_Kit and WinDroid Universal HTC Toolkit
6) I turn off fastboot in settings of my phone
7) I'm trying it on win8 64b
And still I have problem with "no device found"
In cmd if I run adb devices and I got response. If I try adb reboot-bootloader phone is reboot into the bootloader. In device manager before restart phone into the bootloader I see my phone. It's OK but after reboot into the boadloader my phone missing. I don't known if I'm stupid or what but in all tutorials in the internet is that after reboot phone into the bootloader the phone is still visible and I can run fastboot oem get_identifier_token . But for me it is not working. Where I'm doing mistake? Please help me. Thank you.
Edit: I bought my phone by T-mobile. Can be problem there? I mean any strange version of android by T-mobile? Can I reinstal OS for clear Android for htc desire x? thx
Click to expand...
Click to collapse
It's an issue with windows8.1, i also have this issue. hope someone can shed some light on this as all drivers i have tried don't work either
Will_Xda said:
It's an issue with windows8.1, i also have this issue. hope someone can shed some light on this as all drivers i have tried don't work either
Click to expand...
Click to collapse
Thanks for your answer. Hmm, it isn't good . I'll just repair my another computers and create root there.
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!