In an effort to access more storage space for apps I used a text editor to change "dev_mount sdcard/mnt/sdcard" to "dev_mount sdcard /mnt/extsd" and "dev mount extsd /mnt/extsd" to "dev_mount extsd /mnt/sdcard" in system/ect.
which resulted in a bootloop. Attempts to use ADB give this result:
[email protected]:~$ sudo adb shell
[sudo] password for daryl:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
probably because usb debugging is not enabled.
this android is not CWM or TWRP compatible either.
Any suggestions or pointers to get out of this loop would be greatly appreciated.
TIA Daryl
Related
Hi all,
following error when running the command "adb shell reboot bootloader" from command prompt:
* daemon not running. starting i
* daemon started successfully *
reboot: Operation not permitted
Been trying for long time now to flash but no luck so far.
Thanks in advanced!
I have an Aria and I rooted (idk exactly how i did it).
I have htc sync and adb install on my win7 machine.
I used superoneclick the first time I rooted my phone.
I got my wife the same phone. I went to root it, superoneclick worked (so I thought).
I went into reboot into recovery and I end up with the UPSIDE RED TRIANGLE WITH THE EXCLAMATION MARK!!!!!!!!!!!
I wipe my machine free of HTC and rooting product. Reinstalled adb and then used revoked and am still SOL.
I have superuser installed and have rom mananger installed, but I cannot get into recovery. ROM Manager even installed the latest clockwork mod.
But I'm getting the UPSIDE RED TRIANGLE WITH THE EXCLAMATION MARK!!!
HELP!!!!! PLEASE!!!
I tried to unroot with superoneclick and this is what I get:
Code:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
48 KB/s (5392 bytes in 0.109s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
OK
Removing su...
rm failed for /system/bin/su, Directory not empty
OK
Removing Superuser.apk...
rm failed for /system/app/Superuser.apk, Directory not empty
OK
Removing Superuser.apk...
Failure
OK
Remounting system with read-only access...
error: device not found
FAILED
I tried it again superoneclick froze on me.
check out the Aria Superthread Guide
I'll give it a whirl....
OK the .exe stops downloading from megaupload at 33.4mb. I even bought the premium.
Any other ideas?
SOLUTION!!!
So I found the ROM on the HTC site:
http://www.htc.com/us/support/aria-att/downloads/
I flashed it.
Then I got this error:
Code:
Internal error: am reported error starting service
I googled it and I found this forum:
http://androidforums.com/aria-all-things-root/248603-unrevoked-error-am-reported-error-starting-service.html
Great success!!
I reverted unrevoked to 2.1 and it worked!!!
glad you worked it out
Went from stock Wifi Only US Honeycomb 3.2 non rooted to Tiamat Katana 2.0 via this method below.
I had a few hicups and now I'm wondering if anyone can enlighten me on where I went wrong.
First Unlocked and Rooted my Xoom Wifi via this thread
http://forum.xda-developers.com/showthread.php?t=1170760
Code:
PROCEDURE
* Download and place rooted boot image file, superuser.apk & su binary in the same place you will open your command window.
*
Open command window and type; adb reboot bootloader
*
Type fastboot oem unlock and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
*
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
*
In the command window on your PC type; adb reboot bootloader
*
Type; fastboot flash boot rootboot.img
*
Type; fastboot reboot
*
Allow the xoom to boot completely
*
In the command window on your PC type; adb remount
*
Type; adb push su /system/bin
*
Type; adb shell
*
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)
*
Type; chmod 4755 /system/bin/su
*
Type; exit
*
Type; adb push Superuser.apk /system/app
I then installed Rom Recovery. Let it install Clockwork Mod Recovery. I Backed up my xoom with Clockwork via Rom Recovery.
I then downloaded this Tiamat Kernel zip file
Version 2.0.0 "Katana" - Stock GPU
MD5sum: 1fd6a9dfe9c977d53483cb87be258687
see this thread...
http://forum.xda-developers.com/showpost.php?p=11798679&postcount=2
Copied that file to my actual Xoom's internal drive (not the micro SD card).
*** Maybe this is why I was having problems?! ***
I then rebooted into Clockwork Mod Recovery..
Selected Install Zip, Selected the Kernel file Zip, Hit Yes...The install process completed (saw the Tiamata logo, installing...ect).
reboot...
No changes. I would check /system/lib/modules and there would be no new modules there (1 module only). Also, Android's about screen wouldn't mention any change to the version. So I assumed it wasn't installing.
Tried this about 5 times with the above version... still no luck. The kernel just didn't seem to want to install.
I also tried mounting sdcard first then install zip. After rebooting no changes.
I even tried it once by mounting the system which seemed to work, but then my WIFI wouldn't work (no internet connection error) so I guess certain files didn't copy over or didn't have the right permissions.
At that point I just recovered via clockwork with the first backup which must have mucked up some permissions (superuser not working now). I then from adb shell tried...
su
chmod 4755 /system/bin/su
which fixed things..
I then tried a different kernel version from
http://forum.xda-developers.com/showpost.php?p=11798679&postcount=2
Version 2.0.0 "Katana" - Overclocked GPU
MD5sum: f6d64e4e81d2ac050ac1c603b1dbae84
once again copied (was already on my internal card) to the xoom. I might have selected *mount sdcard* first before installing zip via clockwork this try.
Rebooted. Everything installed properly. I now have CIFS working correctly via cifs manager and Tiamat version showing correctly now in Android about settings.
So was trying to install from the internal drive the issue?
Always microsd card to flash stuff, never internal memory.
i attempted to change the stock wallpapers on my kindle fire with APK multitool then changing the stock photos.
the only thing is, i did the replacing of framework-res.apk using root explorer (i had no idea that would be the stupidest thing i ever did)
is there any way to revert the framework-res.apk? my pc doesnt detect it and neither does adb devices.
thank you!
Same problem here... Boot Loop after modifying wallpapers
I did the same exact thing changing my wallpapers on my KF (modifying the framework-res.apk file, copied it back and it instantly started to boot loop). I am also stuck in a boot loop. Have you found a way out of it yet? I can see the KF in ADB and the KF Utility, but I don't have write permissions, and I can't remount to fix it. When I run the KF Utility then (latest version as of today) I get the following (showing only the errors):
BurritoRoot is not installed...
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
2079 KB/s (217261 bytes in 0.102s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
adbd cannot run as root in production builds
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
<idme> Invalid permission
reboot: Operation not permitted
And when I try to do a remount in ADB I get the following: "remount failed: Operation not permitted"
Any ideas? Anybody?
Hi all. I'm running my g2x on tonyp's Paranoid android Ics build (the last one) and I'm getting problems with adb. Everytime i use adb pull or push i get error device not found.
example
1|[email protected]:/ # adb pull /sdard/home
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
If I use reboot or top it works but pull or push doesn't work. I'm still new to adb so any and all help would be appreciated, also I'm using lubuntu 12.10 32 bit.