Develop Bugs

[Q] Bricked need help....

So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...

First of all, what recovery are you using?

Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
/data/local/tmp not /data/local/temp

soupmagnet said:
First of all, what recovery are you using?
Click to expand...
Click to collapse
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system

Bornxero said:
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system
Click to expand...
Click to collapse
It is important to know because the newer ICS roms won't work with CWM, only TWRP.

from the screenshots ive seen of twrp looks like it was cwm...I just want to be able to restore to stock first then I'll do another rom via twrp...

I previously loaded the hellfire ICS without issue as well...

Hey is it a 3.0 kernel from like energy's, I ,may have your answer then. I just need to know if thats the issue you are having.
Sent from my Amazon Kindle Fire using Tapatalk 2

Bornxero said:
I previously loaded the hellfire ICS without issue as well...
Click to expand...
Click to collapse
How recently? Trust me, from what I've seen here, you need TWRP. None of the 3.0 kernel based ICS roms work well or at all with CWM these days, including Hellfire.

Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.

Yea its was a 3.0 kernel...gedeROM..

forest1971 said:
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.
Click to expand...
Click to collapse
I deff. tried everything in the kindle unbrick utility if thats what your talking about...

Bornxero said:
I deff. tried everything in the kindle unbrick utility if thats what your talking about...
Click to expand...
Click to collapse
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.

kinfauns said:
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.
Click to expand...
Click to collapse
w00t solved thanx....i was crying over here lol...
used this to put back the old rom I was using then used KFU to install twrp and installed the new rom without issue....
thanx again....

[ROOT, CWM] JXD S18-03-xxxx RK2926 mini pad [Guide]

In this guide i will show you how to root a JXD S18 03-xxxx device.
This method was tested on the following device:
OS: Android 4.1.1
Kernel: 3.0.36+ Feb 2
Soc: Rk2926
Model: S18-03-201304-4GB-00727
Root:
0. Download files.zip(from here) extract it and open it in explorer.
1. Connect your device to your computer (micro-usb)
2. Unmount all storage devices (TF/SD card, onboard TF/SD, etc..)
3. Enable USB Debugging (Under settings > Options for developers > Enable USB Debugging)
4. Open ''AdbDriverInstaller.exe'' and install the universal ADB driver
5. Automated process for rooting the device ''ROOT ME.bat'' Press any key and just wait and let the tablet reboot.
6. Manual root:
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
And now you have root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure to update su(super user) after rooting. Because it is outdated.
You can either use adb push for this or you can use the Google Play store to download the latest bin.
CWM-recovery
Download: http://files.androtab.info/rockchip/rk2928/20130425/S18-03_CWM.zip
From adb root shell
1. extract flash_image and recovery.img from CWM.zip
2. put flash_image and recovery.img into device, e.g.
adb push flash_image /dev/
adb push recovery.img /dev/
3. enter root shell (adb shell)
4. flash recovery.img into recovery partition with flash_image, e.g.
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Read this when you have any issues
CWM installation problems, please try another method if this doesn't work for you.
Link: http://androtab.info/clockworkmod/rockchip/install/
If you have any issues while rooting please try:
adb kill-server
adb devices
And see if the devices is listed after killing the server.
If it is not than u may have another soc (older version does have other rockchip and the adb driver wont work properly).
This guide is for the latest version as if 1st May 2013: S18-03-XXXX (4.9.2013)
If you still have no output from adb devices you can try one more thing!
By editing android_winusb.inf in C:\Windows\System23\Drivestore\Filerepository\android_winusb.inf_amd64_neutral_<random_chars>
You will see two of those folders.
Open it with a text editor like notepad++ or notepad make sure you have nt authority rights
android_winusb.inf:
Code:
;------------------------------------NTx86------------------------------------
[Google.NTx86];
For loopback testing
And add this after the first space of declaring hardware ids;
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Tested and working on the following devices:
Audiosonic T-17B 7" tablet (Kmart webshop version) ✓
S18-03-XXXX (4.9.2013) ✓
S18-03-201302 (4gb-00905) ✓
S18-02-XXXX (x.x.2012) ?
Credits: me, icood70pro, fun_ for modding CWM for rockchip, all credit goes to original CWM author koush and all its contributors.

How about S18-02-xxxx ?
I got myself a S18-02-xxxx, The ADB drivers behave oddly for this gadget. The driver installs, but SuperOneClick can't locate the device.
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Think you can setup something?

macrat said:
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Click to expand...
Click to collapse
Can you get access to adb shell and what os are you running? Modified adb doesn't seem to work properly on windows 8 you need to change this in order to make it work for windows 8 i think (at least you can try).
Start -> Run -> Type: "gpedit.msc" (Without quotes) -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> Turn off Application Compatibility Engine <- Disable this
It might be the S18-02-xxxx. Model 02 has another soc i think, can you download a app in the play store for me? Type in: "Cpu info", download and install -> "CPU / RAM / DEVICE Identifier". And tell me what soc you have in it. Because the older versions may have a a9 amlogic 8726-m3l soc in it.
Please try that and verify if that worked for you or if you get adb shell access. Thanks,
and sorry for the late reply.

Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?

switchblade88 said:
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
Click to expand...
Click to collapse
Yes i can and sorry for that mistake. Thanks for confirming that it did work for you on another device with the same soc.

Resquest download password
NiTrOwow said:
0. Download files.zip(from) extract it and open it in explorer.
Click to expand...
Click to collapse
I not success download the zip file because ask me for a password. It's possible obtain this password please?

Stef20 said:
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Click to expand...
Click to collapse
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
And my content does not even include <br /> == space/enter ...
FYI. PROBLEM IS SENT TO FORUM ADMIN.

Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!

Stef20 said:
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Click to expand...
Click to collapse
Alright man good luck and let me know if it works for you and let me know the model number

I will for sure. I wait a new tablet S18 from China just I'm not sure if I will have a s03 or s02 model. I suppose is a S03.

NiTrOwow said:
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Click to expand...
Click to collapse
Thanks. This problem is now fixed. it will not ask for a password now.
Mike

Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
MikeChannon said:
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Click to expand...
Click to collapse
Thanks Mike that was fast :')
Sent from my HTC Sensation using xda app-developers app

NiTrOwow said:
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
Click to expand...
Click to collapse
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.

Stef20 said:
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Click to expand...
Click to collapse
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:

NiTrOwow said:
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
Click to expand...
Click to collapse
It's fun view the inside without open it I view have a little more space for a bigger battery

Stef20 said:
It's fun view the inside without open it I view have a little more space for a bigger battery
Click to expand...
Click to collapse
Forgot to say that this battery for the S18-03 has a pcb on the battery (fail safe, anti-overvolt). It did surprise me because most cheap china products don't have that and it is a risk if you want to use it a lot because it may someday explode if you don't have this haha .. Battery looks like a BL-5B/BLC-2 from nokia without the plastic housing.

Finaly I received my S18 today and it's a S03, just a big trouble... after only few hours of use, the power button refuse work now... It's a cra* product I received...

I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.

Stef20 said:
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Click to expand...
Click to collapse
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.

NiTrOwow said:
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
Click to expand...
Click to collapse
I wait a new S18, just it's very long to receive it with the cheap post chipping.
I want root it because I hate not have the control

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks

Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel

Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..

Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file

Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/

Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.

Re-Mi has helped me solved my issue! Thank you so much!

Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!

[Q] Soft bricked htc one m8 no OS

Looked all day for a similar situation and all the ones i found didnt help so this is my last resort.So today i decided to root my phone. I had great succsess and was eager to flash a new rom. My recovery is TWRP. I downloaded Android revolution hd to my external sd. I went into recovery mode swiped my rom, tried to flash Android revolution, the file was there but the image wasnt. Now i have no rom on my phone and cant figure out how to flash one using adb on terminal. The commands ive tried arent working and i get different results from others in similar situations. In fastboot it says 'fastboot usb' so i know its connected and the cables fine. Im definitely a noob at tech hence the reason i managed to make a stupid mistake like this but i could really use the help. Im a US Marine and need my phone by tomorrow. Sorry if this thread is in the wrong spot im new to forums. Thanks a lot guys.

What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd

ckpv5 said:
What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd
Click to expand...
Click to collapse
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?

zacks94 said:
.... i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
Push the ROM.zip to internal sdcard
How-to :
Put a ROM.zip in your adb/fastboot folder
Put your device in TWRP recovery mode
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/
Once complete, select install - make sure the Storage selected is Internal Storage - you should see the ROM.zip

i will try this and get back to you. I appreciate the help.

zacks94 said:
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
If it's not picking up your phone in adb try redownloading the drivers, this website worked for me (http://www.andromods.com/download-files/get-htc-one-m8-usb-drivers-newest-all-models.html). Then try to adb push a stock rom to your device and redownload it in your recovery.

this is what i got and have gotten multiple times with different zips.

zacks94 said:
this is what i got and have gotten multiple times with different zips.
Click to expand...
Click to collapse
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/

1163
ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb

ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
woops. Ths...

zacks94 said:
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb
Click to expand...
Click to collapse
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

zacks94 said:
woops. Ths...
Click to expand...
Click to collapse
I don't know much about Mac, usually the different in command is only put the ./ infront of adb or fastboot
do you get your serial no and the word recovery when you run
./adb devices (put your device in recovery)
this is mine
View attachment 2913050
I tried to adb push HTC_One_(M8)_-_MaximusHD_7.0.0.zip /data/media/0/
(because I don't have the same ROM.zip as yours)
View attachment 2913055
And it is a successful effort

ckpv5 said:
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
View attachment 2913038
Click to expand...
Click to collapse
holy crap it worked. Thanks a lot.I really appreciate it.

zacks94 said:
holy crap it worked. Thanks a lot.I really appreciate it.
Click to expand...
Click to collapse
No problem ... glad that I could help

NO os. stuck in htc logo with CWM but device not recognized adb
ckpv5 said:
No problem ... glad that I could help
Click to expand...
Click to collapse
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul

rauliroo said:
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul
Click to expand...
Click to collapse
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same

ckpv5 said:
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same
Click to expand...
Click to collapse
It didn't work. I genuinely don't know whats missing. if device its not recognized. could be a driver issue on mac??
have a look at the screenshots
many thanks
Raul

Yep .. driver looks ok but you don't have fastboot & adb files ?
See this to get them : .http://forum.xda-developers.com/showthread.php?t=2390995
You mentioned you downloaded sdk, you need to run the command from platform-tools folder.
Check the screenshot how the directory looks : http://forum.xda-developers.com/showpost.php?p=55062969&postcount=10
You should have something like Rauls-MacBook-Air: platform-tools~Raul$ ./fastboot devices
BTW this is M8 forum ... why don't you post your problem in M7 forum ?
Maybe there are more people who familiar with Mac ... I never use one, I know only some basic.

Helo. Can't perform any commands via shell on bueller-5.2.1.0-rooted_r1, 1st gen box

Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title

seems like there some SU related issue.
is that how its supposed to look in the application manager?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrwp said:
Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title
Click to expand...
Click to collapse
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
mrwp said:
seems like there some SU related issue.
is that how its supposed to look in the application manager?
Click to expand...
Click to collapse
Thats how it looks on everyone's. With rbox roms you cant open supersu app.

KLit75 said:
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
Thats how it looks on everyone's. With rbox roms you cant open supersu app.
Click to expand...
Click to collapse
yeah I did type 'su' quiet a few times untill su popup appeared and Im not sure what was wrong untill then, but it worked on the next day itself kinda. at least I dont recall doing anythng specific for it to work.
still not able to start the full unlock procedure tho, gives me the same error even with root prompt

screenshot

mrwp said:
screenshot
Click to expand...
Click to collapse
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.

ImCoKeMaN said:
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.
Click to expand...
Click to collapse
I am running adb push from my machine, from adb shell

mrwp said:
I am running adb push from my machine, from adb shell
Click to expand...
Click to collapse
If you don't understand the difference between your pc's command prompt and firetv shell you aren't ready. the command adb push can't be run from adb shell as you are seeing.

I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...

mrwp said:
I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...
Click to expand...
Click to collapse
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.

rbox said:
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.
Click to expand...
Click to collapse
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.

mrwp said:
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.
Click to expand...
Click to collapse
Well you can't downgrade... so it doesn't matter.

ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now

mrwp said:
ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now
Click to expand...
Click to collapse
If you were on 51.1.1.0, then you already unlocked...?

rbox said:
If you were on 51.1.1.0, then you already unlocked...?
Click to expand...
Click to collapse
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall

mrwp said:
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall
Click to expand...
Click to collapse
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.

rbox said:
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.
Click to expand...
Click to collapse
cool, then I'm all set. still lots of things to grasp though.
thanks a lot!

Did you find a fix?
Hey, just curious to see if you found a fix for this. I had a similar issue. I upgraded my friends AFTV to os5 from 3. Everything was unlocked and rooted but something went wrong when installing Xposed. Basically I didn't realize I had a boot issue at first and it didn't take. Now the AFTV skips TWRP and just goes into the normal AFTV OS. The OS still seems rooted just doesn't bring up the recovery. But I also cannot ADB into it either. Keep getting permissions errors.
Any idea to fix this? Or any idea on how to even connect into it again?
Also here is what I posted on AFTVnews when it happened:
"Wat happens if you sideload xposed before installing the installer it in TWRP? Because I did not read (and did just that (Step 3 before step 2) though I did not launch it) and side loaded it. Now I my AFTV 1 skips TWRP and just goes into the Amazon Home Screen. I also keep getting permission errors in ADB. Also says [email protected], instead of [email protected] Is there anyway to reverse this? It had TWRP running and newest RBOX FireOS5. I’m not bricked, just lost boot to SPMC and recovery access."
AND
"Correction, it’s “127|[email protected]”"