Develop Bugs

[Q] Concern before continuing install of custom ROM....

Alrighty..... I've read / had open the posts regarding ADB, Unrooting, Nandroid, etc multiple times, and I want to make sure things are OK / voice some concerns before I continue.
I've installed the USB drivers needed (installed those only, did NOT install the rest of the components).
Ran SDK setup, edited the android_winusb.inf (have original as .bak)
Had USB Debugging enabled
Confirmed Android Phone listed in Dev. Manager as Android Bootloader Interface
Ran UnrEVOked3 reflash tool, without difficulty, and phone finished in koush clockworkmod recovery, and rebooted.
Used Nandroid Backup to backup to SD card, later confirmed via exploring SD card for confirmation with observing clockworkmod folder. Afterwards, reset back to "Charge Only"
At this point, I wanted to confirm root, and using ADB shell in command prompt typed in at $ su and was rewarded with the response of su / Permission denied / $.
A bit concerned, I rebooted the phone, everything works (well, I don't directly observe any issues, can make / receive calls, texts, etc).
Under "Software Information" I see:
Firmware Version: 2.1-update!
Baseband version: 1.00.03.04.06
I'm very much aware that I need to update the radio, plan on using unrEVOked Forever. I have the option to use Clockworkmod "apply sdcard:update.zip" next.
I'm wanting to make sure things are "OK" and the phone is sucessfully "rooted" before I carry on.
I have no doubt this is the "umteenth" thread, but it's my first "smartphone", and my first time doing this, so please be gentle, it really is my first time
Thanks for any time on this, and posted responses.

If you got permission denied when running su in adb shell the your root didnt go correctly. It should of just dropped you to a # prompt. When you typed su did you then go to your phone and get the popup by superuser asking if you allow or deny? Did you select allow?
while in adb and typing su it should look like this
Code:
$su
#

I never got the option, or I didn't see it. ::Confirmed::, I still get the $ after typing in su
Another question: Should I install the packages listed in the SDK update as well? I have 2.2, API 8, revision 2, 2.1-update1, API 7, revision 2, and 1.6 listed, and 2.1-update1 is listed as my latest firmware
**Update** Via unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery, I see device listed with (recovery) next to it. I presume with the 3 files listed to download, I place them in the root of my SD card?

I think that $ is normal on the stock rom with the phone booted up. Your nand is still locked because you haven't done the unrevoked forever, yet. Boot into recovery and do it and you should get the # root prompt. Sounds like you're on the right track.
Typed on my Incredible phone!

Last question (I think)....
I'm assuming that I rename unrevoked-forever.zip to update.zip, and thats the file that I place in the in the root of my SD card, reboot into recovery and select apply update?
#
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
#
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
#
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
I have a feeling I'm misunderstanding some part of that, but I want to make sure before I finalize this.

Does this look good for a final step?

***Update****
Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.
I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?

HyperTension said:
***Update****
Applied Forever Patch, no issues what so ever. Phone loads back to previous states, now I get the # after su request in shell.
I"m still seeing a Baseband Version of: 1.0.03.04.06. The next step is to update the radio, then off to a custom ROM of my choice?
Click to expand...
Click to collapse
Correct. Be sure to do a nandroid before you do each thing. I know it sounds silly and like a lot of backing up, but you'll be glad you've got it if something goes wrong. You can almost always get back to good with a nandroid backup.

Isnt that the truth
Takes 5 minutes to backup, and 5 seconds to break lol. NANDROID

I have not had a chance to flash the radio / install a custom ROM, but everything works!
Big thanks for the support / guidance through this!

Next question, obviously asked in several previous threads, but I'm unable to resolve the next issue at hand with that data.
When I power on, and hit hboot, I'm still seeing S-On, yet if I log into abb shell, su, I get "#", as well as now having the icon for "Superuser Permissions".
I've attempted to install the radio update "PB31IMG.zip" via root of SD card. I'm able to see / install it, yet baseband is still showing 1.00.03.04.06.
I have W7, and have the option to "Hide extensions for known file types" off (Can't stand not seeing exactly what files are what).
What am I missing? I've seen that others have had to do the "*22899 then *228 option 2", yet If it doesn't show it as being a valid install, I'm hesitant to try and reinstall it
****Edit**** If this is the case, then I will wear the obligitory "dunce" cap for a bit.... Do I need to rename PB31... to update, the port over to root of SD and install then select "apply sdcard:update.zip"?

[Q] unrevoked worked but phone still not rooted?

It took me 4 hours to get unrevoked root my phone (turned out that the actual version is buggy) but somehow it seems not "really" rooted.
I want to install titanium backup, so when I start it I get this popup to grant root access but titanium still says it is not ok.
I can do a "su" in the shell but not a whoami. - I don't understand why.
If I go into the recovery menu it says ClockworkMod Recovery v.3.0.0.5
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp-031d
Radio-5.10.05.23

If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide

EddyOS said:
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
Click to expand...
Click to collapse
It even says on first Titanium Backup launch!

Yep...pops up a message. Click "Problems?" at the bottom for a reliable busybox.

Believe me I bothered a lot to look around and I tried for hours and hours.
Titanium complained about not having root privileges not about busybox. And in the help on their homepage there was this guide "how to check if your phone is rooted properly" by issuing the su command followed by whoami which is obviously misleading.
However, thank you for pointing me in the right direction. It seems to work now.

OK. Now I am convinced - this was completely not my fault. Not only is the documentation missleading, the software is buggy as well.
Going to the Problems? Menu suggests it would fix your issues with busybox by installing it and such...
Well, it does download it to your device but it is not usable until you install it manually via the android sdk in recovery mode. Until then you will not get an app listing. I wonder where to find this little detail in the docu (talking about laziness)

No one else seems to have this issue so not sure what you're doing differently
I just went to running a custom ROM so once rooted didn't have any issues

When you flash your phone with unrEVOked, try using Clockwork 2.5.0.7 as I used this version and it worked 1st time.

SOLVED
Thanks guys. I already solved all problems. It was horribly difficult to get over all these pit falls but finally I reached my goal (a Titanium Backup).
What caused me most trouble was the unclear description of Titanium Backup, especially the part in which they state "if whoami does not respond so and so you are not root"... BULL****!!!
"Short" list of how I got my Desire with HBOOT 0.98 rooted and installed Titanium Backup:
Unrevoked root, but not the latest version 3.32. This one will stop with an Error: Cannot get root. Is your firmware too new? or something similar. Instead use version 3.2
Install Titanium and start it. Superuser will popup and ask for permissions - grant.
Make the changes in the application settings that Titanium asks for (I think usb debugging and allow applications that are not from market) and forget about the message telling you you have no sufficient root privileges, that is not true - I guess what they really mean is that busybox is not installed on your system (would be nice if they'd said what they mean).
Go to the "Problems?" button and let Titanium install Busybox.
... not over yet!
Titanium will now not complain about root privileges any longer but you will still not see any application listings in the software. So maybe there is still something wrong. But what could that be? The root priviliges? WRONG!. Titanium downloaded busybox but did not bother to also install it, although it said it did ;-)
Get the android SDK from Google and install it. (you will also need the Java JDK). You can uncheck most of the packages during installation, probably all. We are only interested in the adb tool that is included in the base installation (I think it is, I also installed the Android SDK Platform tools, SDK Tools and SDK Platform Android 2.2 - just because I was not sure about it).
Boot phone into recovery and connect with the adb shell. (this is a little tool that you will find in the tools subdirectory in the android sdk. You need to start it from the command prompt)
Once connected you need to install busybox manually. Titanium did download the data but did not install! How to do this is described by Loccy here:
Code:
Actually, what I did was use Titanium's busybox:
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Instead of using the mount commands, listed above I mounted the mentioned directories with the mount option in the ClockworkMod recovery menu, that comes with the unrevoked rooting, because the mount commands did not work properly for me. Also, I had to cd into the /data/data/com.keramidas.TitaniumBackup/files/busybox directory and copy busybox to /system/bin/. from there.
Code:
cd /data/data/com.keramidas.TitaniumBackup/files
cp busybox /system/bin/.
cd /system/bin
./busybox --install -s .
But I might have had a typo.
reboot the device and enjoy.
I should mention, if you NOW issue the suggested "su" and "whoami" commands in a shell that according to Titaniums super HOWTO should tell you if you have root privileges, THEN you will get the right response.
In Conclusion:
Forget about the Titanium howto. If Unrevoked finished with no error you HAVE root privileges, no matter what Titanium tells you. Another indicator: If the superuser popup appears, you should be rooted as well.
Install Busybox either completely manually or with the above described method via Titanium. The busybox setup has worked if you can issue the "su" and "whoami" command in a shell.
@EddyOS: "Noone" might not be entirely true - If Titanium was so clear you would not find tons of "how do I install it" questions in the forum. If it works on some *or most* devices but on others not, this is just an indication for sloppy coding. And a user should not have to spend hours over hours to surf some forums for solutions that should have been provided by the developers in the first place. Some people have a life...

[Q] [Solved] Problem re-rooting (running stock 4.2.2)

I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...

ChrisG12 said:
I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...
Click to expand...
Click to collapse
adb reboot bootloader ?? or fastboot reboot-bootloader?? you are supposed to be in fastboot mode.
i dont know if this will make sense: flash latest CWM http://www.clockworkmod.com/rommanager and install latest supersu http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip
open supersu and update su binary
install busybox

2 in a row: OP, read the stickies on general and q&a by efrant before asking questions.
a maguro wrote this.

Actually - I did read the stickies before posting - thanks though. I know how to root - done it on a few devices in the past. Done it successfully on my Nexus in the past too...
For the record, those commands I listed are valid (they are from instructions on Droidlife.com and XDA) - I prefer not to use a "one-click" tool. So I use the Android SDK and run commands from a DOS window one at a time. Also - this way I don't have the custom ROM permanently installed on my phone...
That exact procedure worked in the past - but now it doesn't. I've tried the latest roms, etc. nothing - all the commands seem to run fine but after the phone reboots - I don't have root.
I did at one point try one of the one click tools ("Nexus Root Toolkit") - but it didn't seem to work either.
Has anyone seen this problem? I seem to have two copies of supeuser installed on my phone (one from the previous successful rooting and one from my current attempts) - is that a problem? I can't seem to get rid of them (chicken and egg - need root to remove APK)...

Huh? Superuser? Use SuperSU. Here, check this thread. http://forum.xda-developers.com/showthread.php?t=1538053 - the flashable zip is on the first post. Now, what you should do is, while on a custom recovery, 'adb shell', mount /system rw, delete traces of previous su zips, and then flash SuperSU zip.
a maguro wrote this.

Thanks man - that did it!

ChrisG12 said:
Thanks man - that did it!
Click to expand...
Click to collapse
Please edit thread title to include [SOLVED] after [Q]; reported to mod team for closing.
a manta wrote this.

Kindle fire 8.9 error updating binary in zip

OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!

kyleyarbrough said:
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
Click to expand...
Click to collapse
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
HI! thanks for that advice. I wish I could. I've tried several methods, and although I can get into ADB shell, I can't access su:
besides kindle fire first aide and other batch files, I found some manual instructions:
http://forum.xda-developers.com/showthread.php?t=2277105
Here's what it tells me to do (among many other things): I realize this is just backing up stuff that doesn't exist etc, but it's indicative of the problems without having su.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
but if I go into adb shell and type any commands, like just simple su:
I get /sbin/sh: su: not found
when I do whoami: I get root
but I get a funky prompt:
~#^[[61;5R
instead of a normal # root prompt.
So I'm kind of stuck because I can't really do anything without the su, and it says I'm root. So can I adb push over the files and mount the right drives or whatever to get it to recognize su. At that point I can install twrp, but i'm sure at that point my existing twrp will work too!
I can't seem to get it into fastboot mode either. When I adb devices it says I'm in recovery, not device and in TWRP it says no OS installed. So my only functioning loader is TWRP. (or however you put that more accurately).
I feel like with adb push working, I should be able to do something to get this back, but all the tools expect you to just push a button, not do it the hard way.
So long story short, if you can point me to a thread that tells me how to update TWRP or how to push SU over with ADB or anything that would be awesome. I"m not a complete turd at this, but I think I broke it using something like kingoroot instead of just using the bin4ry while I still had the cyanogenmod working somewhat. So I'm thinking that's why i got the funky prompt, and that's why my su is gone from where it should be.

Fire TV 2 - stuck at b/w boot logo after flashing prerooted 5.2.1.0

Hi folks,
I having some problems here while I try to flash the latest prerooted rom from rbox. So here is the situation
FireTV was on Stock Rom 5.0.5.1
- I followed the Guide on aftvnews to install TWRP Recovery link
- everythink looked good, prerooted rom was installed without any errors
- reboot system -> stuck at black&white "amazon" logo
- I noticed that the LED completly turned off after 30 seconds (i guess) so might be looping
- back to twrp I did wipe /cache, then reboot -> same behavior
- tried over adb shell : mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
-> same result
- tried factory reset -> guess what, same as before of course
so what the hell can I do to reset it in some way?
One thing I also noticed is that when I open a local terminal or an adb shell I'm already root. Is this normal for prerooted rom?
And another thing is the supersu binary. I could remember that the bin was installed to /sbin/su ,but this is not the case here.
'which su' gives no result back
'find / -name su' give me /system/xbin/su
Is that the way it should be? I ask because adblink gives me an error when I try to run FS R/W
"root requiered"
Thats explainable cause adblink will run 'su' first.
I would be really happy if someone could give me some advice. I dont know what else I could try

!! Problem solved
It was the god damn HDMI cable -.-
Behind the boot logo it was waiting for paiing the remote
Maybe it could help some of you guys too
Kind regards

Thank you, had the same issue, never would have tried a new cable, as i was getting video from it.