[SOLVED] Kindle fire rooting error - Kindle Fire General

I rooted it yesterday then I reset the phone
I want to root now the same method doesn't work
when I write
adb root
command it gives me
adbd cannot run as root in the production builds
why??
what is the error is this in files or what

how you try to root your kf?
did you use burrito root3?

*********************
skip to the next replay

yes I tried it with those steps
http://www.androidpolice.com/2012/0...r-6-2-2-update/comment-page-1/#comment-169037

this is my try plz help me
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb devices
List of devices attached
2A9C002600000001 device
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
13 KB/s (0 bytes in 13317.001s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[COLOR="Blue"][1] Killed am broadcast -a ...
[/COLOR]Please run "adb root" and enjoy
C:\kindleADB>adb root
[COLOR="blue"]adbd cannot run as root in production builds
[/COLOR]
C:\kindleADB>

with this method others had also troubles - would try to use burritoroot3:
http://forum.xda-developers.com/showthread.php?t=1410223

Where I will find
BurritoRoot3.bin

look here
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \
C:\>cd android/platform-tools
C:\android\platform-tools>adb kill-server
C:\android\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb push BurritoRoot2.bin /data/local/
13 KB/s (13317 bytes in 1.000s)
C:\android\platform-tools>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>
C:\android\platform-tools>as
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>adb devices
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell chmod 777 /data/local/tmp
C:\android\platform-tools>adb install BurritoRoot3.apk
3307 KB/s (1164225 bytes in 0.343s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
C:\android\platform-tools>adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
[COLOR="Blue"]Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
[1] Killed am broadcast -a ...
Installing Superuser APP, if it errors as already exists, please ignore the erro
r.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[/COLOR]
C:\android\platform-tools>
the blue means no any result

no bin - it's a completly new method - please read the op (1st post) of the above linked in thread
wait - still reading your updated post

okay look to my previous post i tried it and the result is above

everything seems to be fine as in your previous post:
Code:
Installing Superuser APP, if it errors as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
it says you should ignore the error cause you have allready installed the superuser app

yeah it installed
should I continue??AND Ignore this error

YES - it says to ignore the error

Not working!!

what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so

I don't know what happened but someone told me to reset the kf
then when I tried the order that was the output
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
2273 KB/s (0 bytes in 1164225.000s)
[1] Killed pm install /data...
C:\kindleADB>

to restart was probably not the best idea - anyway:
the error message looks like he uninstalled it now
retry:
adb install BurritoRoot3.apk
what's the output ?

b63 said:
what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so
Click to expand...
Click to collapse
thank you so much, i was having a problem with this, i used 2 lines above and everything went smooth
respect

okay I will try now

look
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd \kindleADB
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
216 KB/s (0 bytes in 13317.000s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\kindleADB>adb root
adbd cannot run as root in production builds
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
can't find 'BurritoRoot3.apk' to install
C:\kindleADB>adb install BurritoRoot3.apk
573 KB/s (0 bytes in 1164225.001s)
[1] Killed pm install /data...
C:\kindleADB>

Related

[Q] i need help again

trying too root.. and im looking at this
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
65 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
395 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 19393
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ adb shell
adb shell
adb: not found
$
what do i do now????
The $ means you are still in the shell. You have to wait till it goes back to the Command prompt (c
Sent from my SCH-I500 using XDA App
ace5198 said:
trying too root.. and im looking at this
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
65 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
395 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 19393
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ adb shell
adb shell
adb: not found
$
what do i do now????
Click to expand...
Click to collapse
You haven't waited long enough. That last step should kick you out of the shell, and back into the command prompt, where your 'adb shell' command will work.
adb is used on the windows command prompt, not the phone's shell.
To exit the shell, and get back to the windows command prompt, you can always type "exit" and hit enter at the $ or # prompt.
just wait?
ace5198 said:
just wait?
Click to expand...
Click to collapse
Ideally yes. Many people report having to wait up to 2 minutes. I don't know what you've done since then, best to just start over. To be safe, just reboot the phone, then start again.
ok i rebooted and got past that point now im at this line and stuck
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Valued Customer>cd\
C:\>cd c:\AndroidSDK\tools
C:\androidsdk\Tools>adb push su /sdcard/su
320 KB/s (0 bytes in 26264.000s)
C:\androidsdk\Tools>adb push rage.bin /data/local/tmp/rage.bin
87 KB/s (0 bytes in 5392.000s)
C:\androidsdk\Tools>adb push busybox /sdcard/busybox
410 KB/s (0 bytes in 1867568.004s)
C:\androidsdk\Tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 rage.bin
chmod 0755 rage.bin
$ ./rage.bin
./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2200
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\androidsdk\Tools>adb shell
error: device not found
C:\androidsdk\Tools>
help please.. im totally lost and cant find anything about this anywhere
hahahahah wooohoooo.. i did it... benchmark 2155 =) thank your so much to everyone that helped me... you are all awesome.. tanks dirrk for the step by step instructions..and a huuuuuggggeee shoutout to poulosjr couldnt have done it without you.. thank you all sooo much
Hello ace5198,
How did u do it? I am facing exactly the same issue...
$ chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
$ cd /data/local/tmp
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3341, 3341}
[*] Searching for adb ...
[+] Found adb as PID 1941
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
[email protected]:~/android-sdk-linux_86/platform-tools$ ./adb shell
error: device not found
There is a new root method by dirrk on one of the stickies in android development... I would link you directly, but I can't from my phone. look for the one that says roll up

Stuck in KF boot screen - details

Received my KF about a week ago. Just tried to root it yesterday. That was successful. The instructions I was using said this: "This will “root” your Kindle Fire. You can actually stop here but I recommend you to go to the next steps to install TWRP Recovery, which will allow you to install/backup/restore ROMs and also “unroot” your Kindle Fire when needed easily." So, silly me, without doing further research, went on to the next steps. I almost immediately got stuck, here is the code, ending with the -bash where I was stuck.
Zach:~ Zbhest$
Zach:~ Zbhest$ cd Downloads/KindleFireRootMacLinux
Zach:KindleFireRootMacLinux Zbhest$ mkdir ~/.android
mkdir: /Users/Zbhest/.android: File exists
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/.
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac kill-server
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac devices* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
08EC002600000001 device
Zach:KindleFireRootMacLinux Zbhest$ sh runmemac.sh
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1836 KB/s (23056 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195bb 0xafd39357
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle USB DEBUGGING (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4634 KB/s (1075144 bytes in 0.226s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.038 secs (28293263 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1508 KB/s (22228 bytes in 0.014s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
5116 KB/s (785801 bytes in 0.149s)
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5382 KB/s (3104805 bytes in 0.563s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Zach:KindleFireRootMacLinux Zbhest$
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
restarting adbd as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
260 KB/s (22228 bytes in 0.083s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod -6755 /system/sbin/su
Bad mode
Zach:KindleFireRootMacLinux Zbhest$ .adb./adb-mac shell chown 0.0 /system/xbin/su
-bash: .adb./adb-mac: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ cd Desktop/kindleFireRootNew
-bash: cd: Desktop/kindleFireRootNew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ cd desktop/kindlefirerootnew
-bash: cd: desktop/kindlefirerootnew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
877 KB/s (22228 bytes in 0.024s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
adbd is already running as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xboin/su
264 KB/s (22228 bytes in 0.081s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell cown 0.0 /system/xbin/su
cown: not found
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod 06755 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac install Superuser.apk
3818 KB/s (785801 bytes in 0.200s)
pkg: /data/local/tmp/Superuser.apk
Success
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell
# su
# idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
Zach:KindleFireRootMacLinux Zbhest$ ./fastboot-mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
-bash: ./fastboot-mac: No such file or directory
And now my Mac does not recognize my KF. When I unplug my KF it appears bricked (will not turn on), but when it is plugged into a wall outlet I can do the hard reset, it charges, but does not go past the KF boot screen.
Also, ADB does not recognize any devices.
Additionally, I have a windows 7 machine. I was going to attempt to pick up where I left off, but as my KF is listed as an "unknown device," I cannot update drivers (or do not know how to do so manually). I also installed this little number: http://forum.xda-developers.com/showthread.php?t=1430038
And I currently have linux loaded on my W7 machine. When I try to use the "normal_boot" command, which is advised, I get:
"Resetting bootmode to standard boot...
< waiting for device >
"
So, yeah. That is where I am at. I WOULD go on to the other directions in firekit, but would prefer not to completely void the warranty using the "usb boot mode trick".
If windows 7 is the key here, I may need a walk through for driver installation and such. Otherwise, I am not totally disinclined to call customer service and ask for a replacement. Apparently they have been good about replacing rooted kindles?
Same issue right now... already tried reinstalling windows/firekit liveusb but nothing works=\ Is there any news on this problem?
http://support.microsoft.com/kb/315539/en-us
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I did read all those threads about such problem before. Just no matter what i do those drivers won't install. I only get unknown device on 7/xp and cannot change it coz when i manually select those drives windows says that there no device info in it=\ Thanks for help anyways
did you select adb_usb.ini ? it's just the folder with this file in it. selecting just the folder is usually enough. if you want to select the file: the driver file is android_winusb.inf. there is the harware info
if you have xp available then use this machine - it's easier
Yeah i did select that inf file (it was only one selectable in folder anyway) but it still says same stuff. I have xp right now if that gonna change something
yes xp is easier to handle because:
only 32bit -> only 1 driver version
no user access control -> don't need to do every thing as administrator
please check the following:
you have a .android folder under your user directory - in this folder is adb_usb.ini - the file has entries for device 0x1949 and 0x18D1 - if not run install.bat from the driver set i provided
check your device manager and delete every entry with kindle or adb
unplug and replug your kf - select the driver i provided manually
Got those 0x1949 and 0x18D1 in adb_usb file. And i only have unknown device every time i plug kindle in, no adb kindle at all
right click unknown device - update driver - select android_winusb.inf
if this don't work we have to cleanup old drivers -> could help per teamviewer if you like
When i try to update driver and manually use inf you provided it says that there no device info there=\ And i got unknown device since fresh windows install so idk what driver can cause it -.- I could ve try teamviewer but my windows is not english so it gonna be quite useless.
what language ?
Well it's in russian +there no laptop drivers yet coz im using xp only for this god dam kindle
ok your right - with russian i have a problem
will try to describe you the steps:
disconnect and power off (pwr ~30sec) your KF
open a command prompt
type "set devmgr_show_nonpresent_devices=1"
type "start devmgmt.msc"
Click Show hidden devices on the View menu in Device Manager
uninstall every entry with kindle, android phone or adb device
power down computer and power on again (no restart)
tell me if your done - we will resume ...
ok i did everything step by step tho there was none of adb/android phone/kindle so i just deleted my unknown device.
ok - lets resume:
you may want to delete your old driver set previously downloaded - it must be faulty
now download the one from this post and extract it to c:\
now plugin your kf (don't power it on - will do it by itself)
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
if this don't work eighter then i would think you have a faulty cable !
try an other one ...
Nope still same=\ Guess i will look for new cable tomorrow then tho this one was just fine today at transfering stuff (dam you nokia!). Well thanks for trying to help anyway.
you have the nokia cable - i have the same one
tell me the status your kf now
stuck at boot screen ?
some other tricks:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
if you'r stuck in wrong bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
if you issue the fastboot commands and get <waiting for device> over some while power the kf off (pwr ~30sec) and on. at some point it should recognize the command
Yeah it same as before=\ I have same problem as topic starter aka device in fastboot and windows won't recognize it and install correct drivers. Fastboot commands won't work coz i don't have correct drivers and all they do is stuck on waiting for device/
xx time later = IT WORKS!!! for some weird reason it picked kindle up nothing changed in windows yet it works! Thanks again for your help time to flash recovery again.
courious - just tested on mine
when i switch to fastboot it is recognised as "android adb interface"
not the composite thing !
and i have the same drivers on xp
perhaps you want to try this one:
http://forum.xda-developers.com/showthread.php?t=1428428
sorry - no more ideas ...
UPDATE: hurraaa !!! - wish you all the best and good luck !!!

help with root

Can anyone help me with rooting U8800pro running the official 2.3.5 ?
I tried all the methods I was using for the U8800 but all of them doesn’t work... Any advice ?
i have the same problem, how to root???
linomaniac said:
i have the same problem, how to root???
Click to expand...
Click to collapse
i'm searching everywhere for 3 days now with nothing usefull
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
dancer_69 said:
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
Click to expand...
Click to collapse
i think its not that easy to me to do it manual
but thanks anyway for trying to help
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
dancer_69 said:
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
Click to expand...
Click to collapse
i tried this way but it didn't work too.. i found a prerooted boot.img.. replaced the original one but it didnt work
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
dancer_69 said:
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
Click to expand...
Click to collapse
i got the prerooted boot.img file for the U8800pro... replaced it with the original one.. But the phone is not booting.. It stuck on the huawie logo (the 1st logo before the one with the animation) so i had to put back the original one to make it work
I mean the error on manual rooting.
As fro prerooted boot.img file, are you sure that is compatible with ther rom you have? If is from a custom rom will not work. You need the boot.img of a phone with the same rom as yours, just rooted.
well, maybe it wasn't compatible with my stock rom.. do you have anywhere where i can find some prerooted imgs ?
and about the manual root.. i didnt got any errors coz i didnt know how to wirte those codes :s
Sorry I' don't know because I haven't a pro model and I don't know if there is a rooted boot.img uploaded fro pro mode. Maybe a member with pro read your thread and upload his img file.
-About manual rooting, you need to open DOS command prompt window. It' s in all progarms -> accessories
If you put the DoomLordRoot program in the root directory of your C drive and rename this folder to DoomLordRoot.v3(if have another name), you need to just put the commands one by one as given on the link I posted.
You just need to put first the command:
cd \DoomLordRoot.v3\files
to go to directory in which adb.exe is.
You can check if you are in the right path if you enter the command:
dir
afterwards. If you are in correct folder you'll see the files which are in c:\DoomLordRoot.v3\files directrory listed.
After that just start to follow the directions of the link. Just hit enter after every command you put. If you don' t see errors after every command you're ok. If you get an error on a command, write it here, for farther help. I don' t think that you' ll get an error, because I've done this proccess about 5 times and never get an error. But if you do, just put it here to see if we can help.
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
VaMpYMaSTeR said:
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
Click to expand...
Click to collapse
Put su or sudo before command. like this "su /data/local/tmp/busybox mount -o remount,rw /system"
Yes, seems that you didn' t give the su command before(I think I've include command su, on my tutorial but I' m not sure. I'll check it).
If you see the symbol $ this means that you haven't get root rights yet.
Seems that zergrush succeed, so everytime after adb shell command, first you need to give the command:
su
If device is rooted, you'll see that the symbol changes to #
I think that you' re in good way though.
when i put SU in the begining it give me this :
su: permission denied
if you rebooted the phone you must run zergrush again.
Zergrush is the hack that unlocks the root account temporary. If you didn' t success to put su program on the right place, rooting access loosed after rebooted. su makes root permanent, busybox is an advanced shell and superuser is the app which used to give or denied root rights to apps which asking for this.
First be sure that zergrush is copied to data/local/tmp and you give to it the right permissions(all commands are in tutorial)
These messages mean that zergrush running
[+] Found a GingerBread ! 0x00000118[*] Scooting ...
bugreport dir[/data/local/tmp] exist.[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Click to expand...
Click to collapse
after that check if root succeed by input su command. If you get the # sign you're good to go to continue(exit shell etc)
i'm so sorry, but what do you mean with "If you didn' t success to put su program on the right place" ???? what where is the right palce ?
Some of the commands on tutorial handle the su program.
Push it to /system/bin(this is the right place), change its ownership, permissions etc.
For these commands to succeed(and also the commands for busybox and superuser), first need to enter to root account, by command su:
adb shell (press enter)
su (press enter)
these give the # sign which means that you are root.
If you don' t do this all commands will fail with errors as:
permission denied or cannot write to...
now i'm getting this:
C:\DoomLordRoot.v3\files>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
$
i think i will give up

[Solved] root failed with 6.2.2

my Kindle Fire is upgraded to 6.2.2, I want to root it for the google anroid market and chinese input method.
I pushed zergRush and busybox to KF, but the busybox mount failed. Now, the 6.2.2 can not be root ? or I make some mistake?
adb push zergRush /data/local/tmp
adb push busybox /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 *
./zergRush
$ ./zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$ busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
busybox: permission denied
$
zergrush is'nt working any more - since 6.2.1
use:
http://forum.xda-developers.com/showthread.php?t=1410223
or with kfu:
http://forum.xda-developers.com/showthread.php?t=1458841
Thanks you, b63.
It worked.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Hungover Root [Roots latest version without flashing anything]

Well, I know it's not particularly important since Zergrush still works but I've found an exploit of file permissions on the latest update.
This root causes things to break until you undo it due to it drops you into emulator mode on your phone. This isn't doing anything bad but a lot of things crash and only a few things really work...like ADB. So this is when you install su / superuser.apk and then you just undo it and reboot. Then you'll have superuser installed on your device. This should theoretically work for all samsung Galaxy S devices (Captivate, Vibrant, Epic 4G, etc) so feel free to try and link to this in those forums.
Story behind the root: I was drunk and bored, a friend had the Captivate, and I decided to look and find this.
Instructions! (The fun part!)
Download the .zip file and run the following commands:
Code:
adb push Hungover.sh /data/local/tmp/Hungover.sh
adb shell chmod 755 /data/local/tmp/Hungover.sh
adb shell ./data/local/tmp/Hungover.sh --recovery
After it reboots into recovery hold vol down+vol up + power and it should reboot. After its back up and running do this:
Code:
adb shell ./data/local/tmp/Hungover.sh --setup
after it reboots again, press Volume+, Volume- and Power at the same time, and reboot the system.
One more time with feeling:
Code:
adb shell ./data/local/tmp/Hungover.sh --root
****
After it reboots, run:
adb remount
adb push SuperUser.apk /system/app/
adb push su /system/xbin/su
adb shell "chmod 04755 /system/xbin/su ; chmod 755 /system/app/SuperUser.apk ; ./data/local/tmp/Hungover.sh --undo"
Then you will have root! Do whatever the hell you want at this point! :)
Download:
https://dl.dropboxusercontent.com/u/15069134/Hungover.zip
Changelog:
[code] Initial release 1.0
Credits:
Me for finding the exploit.
mechapanda for letting me potentially break his phone.
This post is mine for ****s and giggles.
It was fun watching my fun go through qemu, although i can't say i'd feel the same if i wasn't doing this on purpose.
Fails on Karbonn A37
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
dockers said:
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
Click to expand...
Click to collapse
're read the OP mate... It's for Galaxy S phones ! So it won't work for your phone
Sent from my SGH-I897 using Tapatalk 2

Categories

Resources