Database Develop

Can someone help me change my boot image!!!

YOU PEOPLE ON THIS FORUM ARE NO HELP!!! (SOME ARE)
BUT I JUST NEED HELP I HAVE THE LATEST DRIVERS THE HARD SPL AND WINDOWS 7 AND EVERYTIME I ENTER THE COMMAND TO CHANGE THE BOOT IT SAYS WAITING FOR THE DEVICE WHEN MY G1 IS IN AND ITS ON FASTBOOT WHEN I GO TO MY DEVICE MANAGER IT EVEN SHOWS AS ADB WITH NO YELLOW MAKRS!!!
WHAT IS THE PROBLEM HOW CAN I FIX THIS PLEASE HELP!!!!
ONE MORE THING WHEN I USE BASIC FASTBOOT COMMANDS IT SAYS SOMETHIN ABOUT "adb is out of date' PLEASEE HELP MEEE!!!!!

Darrien13 said:
YOU PEOPLE ON THIS FORUM ARE NO HELP!!! (SOME ARE)
BUT I JUST NEED HELP I HAVE THE LATEST DRIVERS THE HARD SPL AND WINDOWS 7 AND EVERYTIME I ENTER THE COMMAND TO CHANGE THE BOOT IT SAYS WAITING FOR THE DEVICE WHEN MY G1 IS IN AND ITS ON FASTBOOT WHEN I GO TO MY DEVICE MANAGER IT EVEN SHOWS AS ADB WITH NO YELLOW MAKRS!!!
WHAT IS THE PROBLEM HOW CAN I FIX THIS PLEASE HELP!!!!
ONE MORE THING WHEN I USE BASIC FASTBOOT COMMANDS IT SAYS SOMETHIN ABOUT "adb is out of date' PLEASEE HELP MEEE!!!!!
Click to expand...
Click to collapse
1: don't type in all caps. nobody likes being yelled at.
2: you started another thread for something that you've asked several times? not cool.
3: people on here have been extremely helpful for you, but you start a new thread every time you don't get an answer after an hour of waiting. not how it works.
4: people may be getting upset with you because you're not being a particularly pleasant person either.

grandomegabosses said:
1: don't type in all caps. nobody likes being yelled at.
2: you started another thread for something that you've asked several times? not cool.
3: people on here have been extremely helpful for you, but you start a new thread every time you don't get an answer after an hour of waiting. not how it works.
4: people may be getting upset with you because you're not being a particularly pleasant person either.
Click to expand...
Click to collapse
hes pretty much right on the spot.

hi did you try "adb device" to see if adb can detect

Weird problem - just for your info (be aware)

Hi! Just to share what happened to me recently.
My Legend is now sent to service. Don't know exactly what went wrong, but anyways.. I rooted it a couple of weeks ago. Been installing and trying out some ROMs ju find "the one" for me (I'm not new to this, been using rooted Magic and Hero earlier). Finally, I installed a ROM with busybox..so far so good. Then I rebooted my phone - FAIL! It didn't wake up again!
Finally I managed to reinstall a ROM by running "step1" from unlockr's "how to root a legend"-Guide.. But the phone complained about me removing the SD-card. Figured, maybe it was because of unlockr's (Pauls??) testimage, so i ran the official RUU 1.31 and it installed fine (it didn't before). But no, sd-card was still "removed". tried a secont sd-card, same problem. Bought a new 16GB Class 10 card (previous cards were 2GB/8GB class 4) - No go. So - the conclusion is - my sd-card reader is gone. Not to worry, warranty will take care of it - but has this happened to others? If it has, maybe busybox isn't such a great idea on the legend for now.

Hi, nothing wrong with your phone, just an glitch in software that controls usb.
Happen twice for me after flash/root
quite easy to fix with adb and fastboot and terminal software.
se other post and howtos for usb bricked
just make sure that you got same HTC_xxx number to match your device.
http://forum.xda-developers.com/showthread.php?t=733713
/snakehult

snakehult said:
Hi, nothing wrong with your phone, just an glitch in software that controls usb.
Happen twice for me after flash/root
quite easy to fix with adb and fastboot and terminal software.
se other post and howtos for usb bricked
just make sure that you got same HTC_xxx number to match your device.
http://forum.xda-developers.com/showthread.php?t=733713
/snakehult
Click to expand...
Click to collapse
Oh, thanks.. then maybe I should try it before I send it in I actually read the posts before, but I didn't get how to hexedit the file :s I need the how-to for dummies maybe you can help me with that part?
Edit: I can try this later, need to re-root my phone first.. I have my goldcard at home, I'll do it later tonight (I get off work in 6 hours). I'd appreciate if you could help me with the hexedit thou. Now I get "INFOCID is HTC__Y13"
Edit2: since I no longer have root, is it even possible to root the pgone with the sd-controller disabled? :s
Edit3: This is gonna be a loooong post. sorted out the hexedit anyway, I'll se what I can manage :9 Thanks

Problem solved! Thank you for your help! Got back root, now it's just the flashing part left The problem was, I couldn't see my Sd card - at all. but that was easily fixed with the help of this forum! You're great!

I´m glad to help

[Q] SuperOneClick method not working

Hi guys,
I've looked through the entire LG Revo section and read all the rooting threads. I haven't been able to find any helpful information pertaining to my situation. Even though I'm a noob to this forum, I'm not to forums in general.
I'm getting this message when trying to root:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 2.41s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 12.77s
Waiting for device...
OK 12.14s
2.2.2
Getting manufacturer...
LGE
OK 0.18s
Getting model...
VS910 4G
OK 0.06s
Getting version...
88e871b
OK 0.16s
Checking if rooted...
False
OK 0.27s
Installing BusyBox (temporary)... - Step #1
29 KB/s (1062992 bytes in 35.216s)
OK 35.49s
Installing BusyBox (temporary)... - Step #2
OK 0.09s
Rooting device... - Step #1
58 KB/s (585731 bytes in 9.808s)
OK 10.08s
Rooting device... - Step #2
OK 0.08s
Rooting device... - Step #3
OK 0.08s
Rooting device... - Step #4
Failed to set prot mask (Inappropriate ioctl for device)
OK 0.09s
Rooting device... - Step #5
OK 0.18s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED
I've turned the phone on/off and that still hasn't got me rooted. I've also taken out the SD card. Any help would greatly be appreciated. Thanks ahead of time!

root got blocked by the update the revolution just had

vabeachfc3s said:
root got blocked by the update the revolution just had
Click to expand...
Click to collapse
I'm currently running SW Version VS910ZV4. As I was trying to root my phone, a new SW Version tried to start and download. I put it off for another two hours, hoping I could get my phone rooted before that.
Is there any program/method for rooting with the newest software?

The whole reason for me wanting to root my phone was to be able to use the 4G Hotspot. I'm still on the unlimited data plan and would like to be able to use my laptop anywhere with my phone....especially at work.
Is there another way to use the hotspot without rooting your phone? If so, I might go that method.

did u install the lg drivers for your machine?

vabeachfc3s said:
did u install the lg drivers for your machine?
Click to expand...
Click to collapse
Yes, I installed them from the PDA.net website.

your using the wrong superone click
go to this link http://forum.xda-developers.com/showthread.php?t=803682
now go to the bottom of the post and download superoneclick 1.7
this should get you rooted
make sure you have usb debugging checked. the correct drivers installed for your machine. if on a desktop try putting the usb in the back of your tower

report back with results

Will do....right now I'm running SuperOneClick version 1.7 like you suggested instead of the newer version. I'll just show you what I've got so far. I've been waiting on this screen for about 3-4 minutes now...
SuperOneClick v1.7.0.0
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
83 KB/s (585731 bytes in 6.838s)
OK
chmod psneuter...
OK
Running psneuter...
Does it matter whether I use psneuter or rageagainstthecage? How long should this entire process take?

just run the default one first. if it fails try the other rage or psneutor

maybe 3 mins tops

vabeachfc3s said:
maybe 3 mins tops
Click to expand...
Click to collapse
Waited about ten minutes....still nothing. I closed out the SuperOneClick program. Tried running with the rage setting....same results as the first.
I'm not sure what to do...

try rebooting the phone and computer

I thought it was gingerbreak we used instead of psnueter? I have a terrible memory sometimes though...

SteveKran said:
Waited about ten minutes....still nothing. I closed out the SuperOneClick program. Tried running with the rage setting....same results as the first.
I'm not sure what to do...
Click to expand...
Click to collapse
I rooted my phone last week with 1.9.1 ....
After trying four times...only fourth time it rooted the device...the first three times it was hanging like you had mentioned for 10 mins..I basically forced closed it...there is another trick..
this is what i did..if this is helpful to you..
....downloaded 1.9.1..
then downloaded : LG VZW_United_WHQL_v1.2.0 from lg site...
Then connected the phone, selected internet connection (for USB connection type)
the opened up s1c, clicked root..and then
When it says: Starting ADB Server...kept doing the below pattern until i saw Waiting for device..." again
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
When i saw Waiting for device..i Turned USB Debugging ON..thats it...and i am rooted...took like 5 mins..hope this helps..

afma_afma said:
I rooted my phone last week with 1.9.1 ....
After trying four times...only fourth time it rooted the device...the first three times it was hanging like you had mentioned for 10 mins..I basically forced closed it...there is another trick..
this is what i did..if this is helpful to you..
....downloaded 1.9.1..
then downloaded : LG VZW_United_WHQL_v1.2.0 from lg site...
Then connected the phone, selected internet connection (for USB connection type)
the opened up s1c, clicked root..and then
When it says: Starting ADB Server...kept doing the below pattern until i saw Waiting for device..." again
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
When i saw Waiting for device..i Turned USB Debugging ON..thats it...and i am rooted...took like 5 mins..hope this helps..
Click to expand...
Click to collapse
Thanks, I'm going to have to give this a try later tonight. I think I just opened a can of worms though.....last night while I was sleeping, the phone upgraded to the newer version. I'm going to have to read the thread where it gets you back to a previous version so I can root it.

[WIP] Finding Solution for 0% Battery

Hello again people
Ok we know there are a ton of phones with 0% battery issue after downgrade from 2.3.4 and root
Apparently is not software related problem since I already try to:
Flash a lot of different firmwares - Doesn't work
Fix the bootloader - Doesn't work
Repair trim area (working trim area from another phone and restore security backups) - Doesn't work
So now the dev of setool is search for a solution for whis annoying problem.
Update 1
Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.
This process is simple:
1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.
Please anyone with an Arc 0% battery issue send me a pm.
+++++++++++++++++++++++++++++++++++++++++++++++++
Please all users with this problem who want to help to this:
1. Download the rar attached.
2. Unpack it and double click to execute.bat
This file just is a command "adb shell dmesg > log_output.txt"
3. Post that log_output.txt file , don't forget to say the model of the phone
For now this can help to identify the problem. Only post logs with 0% battery problem please
Thanks in advance

here is the attached output file
one of the suspects that someone pointed at is
[ 5.085205] Please check boot accessing charger (want 0x50, got 0xac) ***

other form htcmania
http://forum.xda-developers.com/attachment.php?attachmentid=731963&d=1317070430

You mean THIS thread yeah? Why have two threads of logs? Further instructions are in the link for people to follow

Hey nice thread...
Do I plug in the phone to flash mode or fastboot mode?

icet925 said:
Hey nice thread...
Do I plug in the phone to flash mode or fastboot mode?
Click to expand...
Click to collapse
turned on phone and usb debugging checked

Jinx13 said:
You mean THIS thread yeah? Why have two threads of logs? Further instructions are in the link for people to follow
Click to expand...
Click to collapse
Do you want setool support full of questions?????
Is better this tread to end users help with things that the_laser needs to find a solution for this problem

Using Xperia Arc version 2.3.2 build 181
no root..
Hope this can help

Alejandrissimo said:
Do you want setool support full of questions?????
Is better this tread to end users help with things that the_laser needs to find a solution for this problem
Click to expand...
Click to collapse
Yeah suppose but I was pointing out that maybe the_laser won't see this thread hence it could be a bit pointless

what exactly is the 0% battery issue? anyone?
Sent from my LT15i using xda premium

I tried turning on my phone(plugged in charger) and enabled USB debugging. but when I doubled click on execute.bat I get an empty log_output file!

kbadone said:
I tried turning on my phone(plugged in charger) and enabled USB debugging. but when I doubled click on execute.bat I get an empty log_output file!
Click to expand...
Click to collapse
Same here, I fixed it by opening execute.bat and changing adb to adb.exe. Hope that helps.
Here is my log.

Crahzee said:
Same here, I fixed it by opening execute.bat and changing adb to adb.exe. Hope that helps.
Here is my log.
Click to expand...
Click to collapse
Update 1
Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.
This process is simple:
1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.
Please anyone with an Arc 0% battery issue send me a pm.

Crahzee said:
Same here, I fixed it by opening execute.bat and changing adb to adb.exe. Hope that helps.
Here is my log.
Click to expand...
Click to collapse
Thats all I got, not sure what I am doing wrong!
* daemon not running. starting it now *
* daemon started successfully *

kbadone said:
Thats all I got, not sure what I am doing wrong!
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
Check if adb shell command gives you an $ or #
Anyway if you have an arc please help me to fixing trim area to check if this can resolve the problem

kbadone said:
Thats all I got, not sure what I am doing wrong!
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
Don't worry about that now, go help Alejandrissimo! Hopefully we can find a solution with this new method.

this is my log

Alejandrissimo said:
Update 1
Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.
This process is simple:
1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.
Please anyone with an Arc 0% battery issue send me a pm.
Click to expand...
Click to collapse
looks like someone already tried it.
http://support.setool.net/showthrea...wngrade-and-root&p=68959&viewfull=1#post68959
I am not sure how to do it , but i dont mind following the instructions

visarya said:
looks like someone already tried it.
http://support.setool.net/showthrea...wngrade-and-root&p=68959&viewfull=1#post68959
I am not sure how to do it , but i dont mind following the instructions
Click to expand...
Click to collapse
Same ppl
EDIT: So I assume the new method suggested didnt work?

Crahzee said:
Same ppl
EDIT: So I assume the new method suggested didnt work?
Click to expand...
Click to collapse
A method will come up soon... I can feel it.

[Q] Failed executing command 12 NvError 0x12002

Hello all,
I am very new to the community of rooting and am completely lost. A friend of mine gave me this dell streak 7 because someone gave it to him and he was never able to get it to work. I am stuck at "Starting Fastboot USB download protocol" If someone would possibly explain how I might go about fixing this and using it with it's maximum potential I would appreciate it very much. Now although I am very tech savvy I don't have the slightest clue about rooting or loading custom roms so I will have to be talked to like a child until I get comfortable. As of now I have connected the streak to my computer but have yet to have it recognized. That's pretty much as far as I have gotten. I do have a 32gb SD card as well if it needs to be used in the process somehow.
Thanks for all everyone's time and help
Incase the thumbnail does't work here is a link for dropbox
dropbox.com/s/yqc8s4ndybqrwnr/2013-02-25%2009.08.52.jpg

Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964

YAY !
wptski said:
Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964
Click to expand...
Click to collapse
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
I'm thinking the last person who had this device messed it up very badly and now all it wants to do is go into fasboot mode nothing else, i thought I had installed the (Clockwork mod recovery.img) S7-6.0.1.2.img into the recovery using this guide http://forum.xda-developers.com/showthread.php?t=1334487,
After i do that I says done. but nothing happens on the device after is says "Flashing StorMgr partition recovery"
sending 'recovery' (4742 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.010s]
finished. total time: 0.543s

ddg5060 said:
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
Click to expand...
Click to collapse
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)

Where to now ?
giveen said:
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)
Click to expand...
Click to collapse
Yes but exactly how do I do that? I can't seem to figure out where to start the flashing process. All I am able to do with my device is get into fasboot mode, where do I go from there ? I want to use CM10.1
I tried holding vol (+) and power - nothing
I tried holding vol (-) and power - nothing
Thanks again for all your help

Search is your greatest ally. This has been answered a good 50-100 times.

Yes i know
giveen said:
Search is your greatest ally. This has been answered a good 50-100 times.
Click to expand...
Click to collapse
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.

ddg5060 said:
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.
Click to expand...
Click to collapse
Basics of flashing: http://www.youtube.com/playlist?list=PLB99FAE280F618B12

Please help?!?!
wptski said:
Basics of flashing:
Thank you. I will look at these and hopefully it will clear some things up. The problem is that my situation is unique I think. I don't know if maybe i have a broken button or the person who gave it to me really messed it up but all it does is boot into fastboot automatically, although I can get it into NVFLASH mode i don't know what these modes do. Are they both able to flash the system so I can use the device? If so do some files work in one that don't work in the other?
I tried putting the device in NVFlash mode caus I want to put the CM10.1 FW on it, am I headed in the right direction ? The only things that I can launch are "Install JB_Alpha_E.bat" and "NVFLASH.exe" running the Install_JB one opens the command prompt and it looks like it is doing something which is how it looks in the video but then suddenly after it processes some files the command prompt window just closes, am I doing something wrong ?
Click to expand...
Click to collapse

You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.

Failed executing command 12 NvError 0x12002
So because the cmd prompt closes so fast I cannot see the error, so I took a video and paused i played it until it froze right where the message came up.
Here is what it says if failes right after creating partitions blah blah blah
Failed executing command 12 NvError 0x12002
command failure: create failed (Bad data)
bootloader status: fatal failure to read / write to mass storage (code:9) message: nverror:0x8 (0x19000008) flags: 0
What does that even mean ? is the device broken somehow ?

Sorry
giveen said:
You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.
Click to expand...
Click to collapse
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?

ddg5060 said:
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?
Click to expand...
Click to collapse
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.

giveen said:
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.
Click to expand...
Click to collapse
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.

ddg5060 said:
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.
Click to expand...
Click to collapse
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.

ddg5060 said:
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.
Click to expand...
Click to collapse
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.

giveen said:
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.
Click to expand...
Click to collapse
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?

ddg5060 said:
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?
Click to expand...
Click to collapse
Only one user has claimed to have gotten out it without returning it to Dell.

wptski said:
Only one user has claimed to have gotten out it without returning it to Dell.
Click to expand...
Click to collapse
Damn, let me guess, he won't tell anyone how to do it either or show pictures of claimed revived device.
As far as dell goes, is it something that they will fix or do they consider the warranty void because of whatever was done to it to make it like that?
So sad and here I thought I was actually progressing in fixing it. Question though, how does something like that happen? Did the person flash it wrong? Or interrupt it while writing some critical process?

Actually he did tell us how to do it, it was just 1 in a million chance it works.