Related
I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.
if yr installing through and use
Make sure phone is synced
Make sure app is in tool file I'd adk file
Make sure when at command prompt Ur in adk/tools file first
Adb remount
Adb push (app.apk) /system/(app/framework)
ok I figured out my problem but fixing it is going to be quite confusing. Looks like I would have to know a lot more than I do to fix it. Basically the adb is not reading the phone as root (or something like that). And the ro.secure is set to 1 which it should be set to 0 to be considerd root. So therefore I have to reinstall a bootimg. Ive been reading it on another forum page but i cant post it cause my account hasn't been verified yet. but it's this forum and here is the thread showthread.php?t=443041&page=2
but it's like french to me!!! If anyone can dumb this down for me I would really appreciate it lol thanks a lot you guys have been so much help in the little amount of time ive been a member to this forum. Thank you
redlinethecar said:
I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.
Click to expand...
Click to collapse
First, put your apk's in your "C:\AndroidSDK\Tools\" Folder
Second open the cmd window and do "cd C:\AndroidSDK\Tools\"
Third do "adb remount"
Fourth "adb push xxxx.apk /system/app/"
that will install them
When remounting I get error
Code:
remount failed: Operation not permitted
but I continue anyway and the
Code:
adb push HTC_IME.apk /system/app
sends the file with no problem but it doesn't install it though.
Here are steps to do if it is not already installed on your phone. However, if it is you can not install when it is already there. I'm not sure how to remove in terminal and everything I've tried it tells me read only blah, blah, blah...
I tried mount -o remount,rw /system---that is suppose to work.
1.Make sure anything you want installed is in
the root of the sdcard..(/sdcard/nameoffile.apk)
2. Download a terminal emulator from the market.
If it installs continue..If not then continue on back to the thread.
3. Open up the terminal emulator. It should ask permission from SU. >Always allow
4. Now type the following
su (hit enter)
install /sdcard/name_of_file.apk /system/app/name_of_file.apk----if it is a system app
If it is a downloaded app then use /data/app
Ok.... well I tried that way also and I get the error
Code:
install: not found
I downloaded the terminal app from the market and entered the commands as you said for ex.
Code:
install /sdcard/HTC_IME.apk /system/app/HTC_IME.apk
Thanks a lot though I wish it could have been that easy.
After having nearly hung myself trying to figure out the whole SDK thing, what the hey ADB was and all that jazz, I thought I would give the rest of the people out there a step by step guide on getting from stock to root in no time. If you follow this guide, you won't spend the hours I did on google, XDA and irc trying to get where I am. This stuff can be confusing, and I am only here to make it less so.
Disclaimer: If you destroy your phone, I take no responsibility for it. You are performing this at your own risk.
I take no credit for the root process itself, there are people much smarter than I who worked on this. I used the method outlined here by jcase. I am simply compiling this and making it easy for people (much like myself) who had no prior experience be able to have root.
jcase said:
Credits (from original post here)
Scotty2, jamezelle, jcase, and all of Team AndIRC
Testers, especially ProTekk and Trident
Thanks to scotty2 for WPThis
Busybox was pulled from a CyanogenMod ROM, source should be available here
psneuter was pulled from somewhere, credit to scotty2, source here
All firmware credit goes to 911sniper
Jaroslav from Android Police for editorial help
If I missed anyone in the credits, it was unintentional and I will fix it soon. Lots of people had their hands in on this project.
Original warnings, posted by jcase:
Pros
Root with read/write access to /system
Ability to downgrade and flash any RUU (i.e. signed firmware)
S-OFF
Fully unlocked bootloader
All ThunderBolts survived testing
Cons
Voids warranty
Could brick your phone if you aren’t careful
The method of rooting your Android device as described in the article herein is solely for enthusiasts and not for the faint of heart.
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
Android Police and Team AndIRC disclaim all liability for any harm that may befall your device, including, but not limited to: bricked phones, voided manufacturer warranties, exploding batteries, etc.
The instructions below assume you already have a strong familiarity with adb command lines – this is not for beginners.*
Click to expand...
Click to collapse
*I made this guide as seamless and easy as possible. I have tested this 4 times now with success each time. Just follow every step to a T and there will be no problems. The warning is there to tell you what could happen if you don't listen very well...
Step 1: Download the Android SDK
http://developer.android.com/sdk/index.html
Step 2: Get into the SDK
After downloading, you should have a package named android-sdk_r10-mac_x86.zip in your downloads folder. Unzip it and move it to your desktop, to make life easier on yourself.
*Stop here right now if you have no idea what terminal is... shame on you, also this might be slightly more technical than you thought. No worries, I am going to hold your hand through it all*
Step 3: Get ADB
You can search as hard as you want to in that SDK and you won't find ADB. It's not there, leave it to google to be smug and leave a "ADB's not here sucka!!" readme in the file... cheeky muppets. Regardless of my personal feelings, You need to get ahold of the ADB. Easy enough to do. Open the tools folder located in the android-sdk-mac_x86 folder. Click on "android" (it's right next to google's smug readme...), and wait until it pulls up the screen seen below.
{
"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"
}
Once you've gotten here, click "available packages" on the left and install Android SDK Platform-tools, revision 3. Let it go through it's process and click close. Now, go back to your android-sdk-mac_x86 and you'll have the folder titled "Platform-tools", open it and, TA-DA! You have adb, don't click it... you don't need to.
Step 4: Prepare your phone for rooting.
Make sure your phone is fully charged before beginning. Go to Menu>Settings>Applications>Developer> and turn on USB Debugging. I had my phone on Disk Drive the entire procedure, I'm not sure if it had any benefits other than convenience, but, granted, it helped.
Step 5. Setup terminal for ADB.
To this point, you haven't had to open terminal on your own. It is probably still open from when you installed the platform-tools folder from the android executable file. If it is, right click (control click) the terminal icon, click new window and then click basic. If you closed it haphazardly (shame on you!) you need to open it. It is located in your application folder, in another folder titled Utilities.
Once you get to the terminal screen, you should see a white box, with the name of your computer, followed by the place your currently "located." A ~ means you are in your home folder. For fun, type the following into your terminal window.
Code:
touch test_file.txt
Now, navigate to your home folder and there is a text file there for you. Pretty neat, eh?
Now, we need to navigate to adb. Go to your android-sdk-mac_x86 folder, open it. Now, go back to terminal, type cd and drag the folder Platform-tools to the terminal window. You should see a green dot with a plus sign in it, that means you can add the folder to the terminal window. It should read something like this:
Code:
cd /Users/Your Computer's Name/Downloads/android-sdk-mac_x86/platform-tools
If you moved the android-sdk-mac_x86 folder (Like I did) after downloading it, it will only be slightly different. (My folder was in my home folder, so it just says /users/my computer/android-sdk-mac_x86/platform-tools)
Once you do this, you are ready to begin.
Step 6: GAIN ROOT!!!!11!!
Take a moment, breathe, cry, caress your phone... No, it really isn't that bad. I am what many consider a hypochondriac, I say I am just more "down to earth."
Glass half empty, half full, etc. we begin. I've slightly modified these to make them usable for us Apple guys. (All that has been changed is the adding of a "./" to the beginning of ever adb.)
Step 1
First, download these files:
RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.0103_2r_NV_8k_1.37_9k_1.52_release_
165253 (md5sum : aae974054fc3aed275ba3596480ccd5b):
Multiupload mirror
GalaxySense mirror
DroidSite mirror
Mirrors for the package (contains busybox, wpthis, psneuter, su, readme.txt, misc.img, and hbooteng.nb0) (md5sum : 3b359efd76aac456ba7fb0d6972de3af):
Multiupload mirror
GalaxySense mirror
DroidSite mirror
Custom RUU mirrors (md5sum : aff07b8256628a175c40938d408fa16f):
Multiupload mirror
GalaxySense mirror
(Personally, I extracted the exploit.zip folder, and the RUU_MECHA to my platform-tools folder so I never had to cd anywhere. I strongly recommend you do the same. I put the Custom RUU [PG05IMG.zip] on my desktop, so I didn't get it confused later in the process)
Step 2
Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:
Code:
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push misc.img /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
Step 3
This step will gain temp root and flash the custom misc.img. Run:
Code:
./adb shell
Now the shell should display "$".
Run:
Code:
/data/local/psneuter
You will now be kicked out of adb, and adb will restart as root. Let’s confirm the md5 of misc.img:
./adb shell
At this point, the shell should display "#".
Run:
Code:
/data/local/busybox md5sum /data/local/misc.img
Output should be "c88dd947eb3b36eec90503a3525ae0de." If it’s anything else, re-download the file and try again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
exit
Step 4
Here you will rename the downgrade RUU (RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.0103_2r_NV_8k_1.37_9k_1.52_release_165253_signed.zip) as PG05IMG.zip and place it on your SD card. Then, run the following command:
Code:
./adb reboot bootloader
Choose the bootloader option and press power; let the ROM flash. When asked to upgrade, choose yes. Don’t freak, it’s a long reboot.
Once done, reboot and delete PG05IMG.zip from your SD card.
**Make sure to Re-enable USB Debugging!!! (Menu>Settings>Applications>Development>USB debugging)**
Set up the two part exploit, to gain root and unlock MMC.
Code:
Push wpthis, busybox, and psnueter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push wpthis /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
./adb shell chmod 777 /data/local/wpthis
Step 5
Next, enter the following commands:
Code:
./adb shell
/data/local/psneuter
To unlock eMMC:
./adb shell
/data/local/wpthis
exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
Code:
./adb push hbooteng.nb0 /data/local/
./adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
Code:
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
Code:
/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #thunderbolt.
DO NOT REBOOT.
Now, reboot your phone and put the custom RUU (PG05IMG.zip) on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
**Make sure to Re-enable USB Debugging!!! (Menu>Settings>Applications>Development>USB debugging)**
Next, run this command:
Code:
./adb reboot bootloader
After it flashes, you will be running release firmware with S-OFF.
Step 7
Code:
Push SU, busybox, and psneuter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push su /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
To gain root:
Code:
./adb shell
/data/local/psneuter
The following will remount /system and set up SU:
Code:
./adb shell
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
/data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Step 8
Install Superuser from the Market.
Reboot your phone. You should now have full root permissions.
Step 9
Finally, install ROM Manager from the market, enter ROM Manager and flash the ThunderBolt recovery.
If you have problems getting SU to work, a couple extra reboots will likely fix it. If you still have problems, come to the chat: irc.andirc.net #thunderbolt or use http://chat.andirc.net:9090/?channels=#thunderbolt.
And there you go. You now have root. That was fun right? The irc is absolutely invaluable if you are having any trouble. The people there are really helpful and knowledgable. They won't talk down to you, just try to help.
Again, thank you to the people who made this possible, You all are awesome. the work that had to be done to make this user friendly is beyond amazing.
If I missed anything, please let me know. I might have missed something, I haven't slept all night.
Quite the thorough walk through. Nice job!
Sent from my ADR6400L using Tapatalk
Looks like a nice walk-through.
I may suggest including all of your steps for configuring the SDK and then simply referencing the official root guide... because if that would get updated then you would have old instructions on this thread.
It is not that hard for people to type the ./ in front of every command...
Alternatively (and recommended), you could provide a more thorough guide and include instructions on adding the SDK platform-tools directory to the PATH environment variable. Once this is added, the user can use adb whenever they want, they do not have to change directories to the SDK! This also allow for using the command without needing the leading ./
I knew people would come in who knew something... You both are right. The problem I was having was the same many of my friends and people on here were having, they kept getting a -bash: adb: command not found. I am working on fixing my .bash_profile, but until I get that fixed, this tutorial is the best I've got.
IISiDeK1CKII said:
I knew people would come in who knew something... You both are right. The problem I was having was the same many of my friends and people on here were having, they kept getting a -bash: adb: command not found. I am working on fixing my .bash_profile, but until I get that fixed, this tutorial is the best I've got.
Click to expand...
Click to collapse
I am excited try try this, thank you so much for writing this up. I get very confused doing these things the first time and didn't realize you could do this on mac by adding the prefix in the commands. So, now that I know that, I am hoping to try it!
One question.....and this is a total newbie question, sorry..... In the steps that have several commands like this one:
Set up the two part exploit, to gain root and unlock MMC.
Code:
Push wpthis, busybox, and psnueter.
./adb push psneuter /data/local/
./adb push busybox /data/local/
./adb push wpthis /data/local/
./adb shell chmod 777 /data/local/psneuter
./adb shell chmod 777 /data/local/busybox
./adb shell chmod 777 /data/local/wpthis
Click to expand...
Click to collapse
Should the commands all be ran individually, or all at the same time just on their own lines? Like, can I just copy all six commands and paste them in just like this then hit enter? Or do I need to run them all one at a time?
gadsden said:
I am excited try try this, thank you so much for writing this up. I get very confused doing these things the first time and didn't realize you could do this on mac by adding the prefix in the commands. So, now that I know that, I am hoping to try it!
One question.....and this is a total newbie question, sorry..... In the steps that have several commands like this one:
Should the commands all be ran individually, or all at the same time just on their own lines? Like, can I just copy all six commands and paste them in just like this then hit enter? Or do I need to run them all one at a time?
Click to expand...
Click to collapse
You hit enter after each of those commands.
I'm AMAZED at how well this went! I'd been avoiding ADB on windows, plus avoiding all the 1-click options as they didn't work correctly on VMWare/WinXp on my Mac Pro. So, I saw this post and decided to take the leap.
THANK YOU!!!! My device is now rooted and working flawlessly.
Nice write up, I completely avoided the whole ADB setup subject, due to a lack of mac/windows knowledge. Glad the community can come through.
Can you please paste in my warnings, full credits and links to the GPL (this part if very important to us) sources if you are going to base this on our stuff. Just take them from the original post please.
~jcase
I ALWAYS had to put the
./
before adb so it would be "./adb" for anything that started with adb. I see you missed it a couple times and that concerns me. I followed the original tut by jcase and put ./adb instead of plain adb and everything worked perfect. Just my 2¢.
bmcclure937 said:
Looks like a nice walk-through.
I may suggest including all of your steps for configuring the SDK and then simply referencing the official root guide... because if that would get updated then you would have old instructions on this thread.
It is not that hard for people to type the ./ in front of every command...
Alternatively (and recommended), you could provide a more thorough guide and include instructions on adding the SDK platform-tools directory to the PATH environment variable. Once this is added, the user can use adb whenever they want, they do not have to change directories to the SDK! This also allow for using the command without needing the leading ./
Click to expand...
Click to collapse
I really didn't realize until today that I could just as easily perform a manual root on a mac as a windows machine. So, I am trying to learn about this, been doing a bunch of reading. I am interested in what you are mentioning about adding SDK platform-tools directory to the PATH environment. On a mac, what environment should I be using? I am a little confused about the options listed on the Andorid Developer website. It seems Eclipse is what everything is all about primarily, but I have no clue which one to use. Perhaps I ought to just not worry about all that right now and just follow these steps to root my TB? I'm not really after doing anything other than rooting and flashing ROMs, so is it really necessary to set all that up?
xCHPx said:
I ALWAYS had to put the
./
before adb so it would be "./adb" for anything that started with adb. I see you missed it a couple times and that concerns me. I followed the original tut by jcase and put ./adb instead of plain adb and everything worked perfect. Just my 2¢.
Click to expand...
Click to collapse
Regarding the ./ Are you saying that we need to use that in front of these commands even though it's not listed in the steps?
adb reboot bootloader
adb shell
Other than that, the steps in this post work, right? I have everything downloaded and got as far as getting ADB, but I don't want to go any further if this isn't really as comprehensive as its made out to be.
gadsden said:
Regarding the ./ Are you saying that we need to use that in front of these commands even though it's not listed in the steps?
adb reboot bootloader
adb shell
Click to expand...
Click to collapse
Yes otherwise i don't believe it will work.
Wow! I really didn't think this would get quite as much attention. I think I need to do some more solid work and clean this up a bit. Now, for the individual responses:
@Gadsden: You're very welcome. I kept thinking, this is impossible! But, with a little Red Hat experience and some awesome google skills, I got this.
@Jayhammy: You're welcome man. Enjoy!
@jcase: Of course I can. I never really thought this would gain so many views. There aren't words to explain how psyched I am to see you talking directly to me... lol, I will give full credit to everyone, as soon as I post this
@xCHPx: I posted this after a long night, with no sleep. I knew I would miss something. The cool thing about that is if you copy and pasted the command without ./ in front of it, it would simply not run. There is really no way to mess this up.
@gadsden (pt.2): Hypothetically speaking, you don't need to do ANYTHING other than what I've listed. If you decide to start developing themes, apps, etc. you'd have to worry about eclipse. I made a mistake on the two things listed there, every adb command must have ./ in front of it. I simply overlooked it when typing this up. There was a lot of stuff to be typed.
thanks for the walk-through!
i have 2 quick questions...
for say like this step:
./adb shell
/data/local/psneuter
To unlock eMMC:
./adb shell
/data/local/wpthis
exit
Click to expand...
Click to collapse
ur hitting enter after shell correct? the /data/... doesnt need a program command like ./adb before it correct? same with all other lines with no ./adb in front of them?
also for this:
Step 9
Finally, install ROM Manager and flash the ThunderBolt recovery.
Click to expand...
Click to collapse
im assuming ROM Manager is in market like Super User but i dont know what flash the Thunderbolt recovery means...could u explain that?
Thanks again!
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
IISiDeK1CKII said:
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
Click to expand...
Click to collapse
Funny, I had the same exact question. I posted it in the jcase discussion and got the answer there. Definitely put that in the OP, because first timers don't know these things!
gadsden said:
Funny, I had the same exact question. I posted it in the jcase discussion and got the answer there. Definitely put that in the OP, because first timers don't know these things!
Click to expand...
Click to collapse
Fixed it, I overlooked it. I guess I assumed that everyone knew what ROM Manager was... lol. I've been rooting since the Droid 1, so I've always been around people who know these things. Sorry for not clarifying though, I hope my new updated post is more concrete.
gadsden said:
I really didn't realize until today that I could just as easily perform a manual root on a mac as a windows machine. So, I am trying to learn about this, been doing a bunch of reading. I am interested in what you are mentioning about adding SDK platform-tools directory to the PATH environment. On a mac, what environment should I be using? I am a little confused about the options listed on the Andorid Developer website. It seems Eclipse is what everything is all about primarily, but I have no clue which one to use. Perhaps I ought to just not worry about all that right now and just follow these steps to root my TB? I'm not really after doing anything other than rooting and flashing ROMs, so is it really necessary to set all that up?
Click to expand...
Click to collapse
You can add the path of the SDK to your $PATH variable. This allows you to run ADB from any directory and not need the ./ in front of every single command.
From terminal, do the following:
Code:
ls -la
You should see a file called ".bash-profile within your home directory.
Edit this file and add the path of your SDK to the $PATH variable.
Code:
nano .bash-profile
Familiarize yourself with editing files in nano if you have not done this before. It is very simple. Once you have edited and saved the file... run this last command to check if the PATH variable now contains the new path.
Code:
echo $PATH
If you get lost or confused... Google is your friend! There is a lot of info on editing the PATH environment variable.
*Please Note* this is not needed for the guide but it does allow you to run ADB from any directory... and without leading ./ in front of all commands.
Thanks for this. I'm going to go to lunch and then get into this. How long did it take everyone to go through this?
bmcclure937 said:
You can add the path of the SDK to your $PATH variable. This allows you to run ADB from any directory and not need the ./ in front of every single command.
Click to expand...
Click to collapse
I've set my path up, and it works when I want it to... but this is easier to do (imho) without getting too far into command line. If I feel I could streamline this by doing such, then I will do so.
edit: And now it is broken again... back to troubleshooting... not quite sure wth I did...
@want a droid: The thing that will take the longest is downloading the files needed. Everything else will take you all of 30 minutes at most.
IISiDeK1CKII said:
yeah, I'll explain that in the post but also here. ROM Manager is a program available in the market. If you go to the market and type it in, you'll see it. It's a top hat with a gear behind it.
After you install ROM Manager, You need to touch the first item in the screen, Flash ClockworkMod Recovery. Then you will be good. I am going to update that now in the OP.
Click to expand...
Click to collapse
IISiDeK1CKII said:
Fixed it, I overlooked it. I guess I assumed that everyone knew what ROM Manager was... lol. I've been rooting since the Droid 1, so I've always been around people who know these things. Sorry for not clarifying though, I hope my new updated post is more concrete.
Click to expand...
Click to collapse
thanks man!
yea im coming from a BB so new to this stuff...i have a PC and im doing long way to learn...doesnt seem hard, simple terminal commands but just want to get everything rights...soon as i do it once, ill be good to go and help out others like u guys
Hi this is my first post on the site and i would appreciate it if anyone could help me with this problem. (I know your probably fed up of hearing about rooting problems but anyway!)
I have succesfully installed ADB and as far as i know it seems to be working properley as i can access the ADB shell on my device.
However when i get to a certain stage of the rooting process it all seems to go wrong.
wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
I have been using the above rooting guide (can't hyperlink first post!) and i cannot get past stage 7 of the process because the 'exit' command doesnt seem to work in Command Prompt (Windows 7) and it is stopping me from being able to exit the ADB Shell. I have tried other ways of exiting the shell such as ctrl+C but this kills ADB completely and i think that it is undoing the previous steps of the guide.
I do get the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
so i think that i have successfully rooted the device but i cannot proceed to push the 'su' file to the device as i can't exit the adb shell, i just keep getting lists of text saying reboot (-n) (-p) and everytime i use the exit command nothing seems to happen and the flashing # symbol keeps coming back.
Has anybody else had this problem? or have any idea of how to stop the ADB Shell with any other commands other than 'exi't or Ctrl+C?
Cheers.
If device is rooted, by writing in command prompt the command "adb shell", must appear the symbol #, if the symbol $ appears the device isn't rooted.
If you cannot use adb from pc, run on device a terminal emulator(you can find one on market) the above command to see if you're rooted. Then you can give the next commands from terminal emulator(maybe you need to copy the nessecary files on sd card and change the related paths to point to sd card)
I'm having the exact same problem while rooting my HTC Tattoo (on Windows 7).
I have Android 1.6 (Donut), the baseband is 13.29a.55.13H_3.35.07.33, kernel is 2.6.29-gf922713 and build is 1.67.173.37.
Please help and thanks in advance . I really want to install CyanogenMod 7...
more info
When i say i have rooted the device i mean temporarily by pushing and changing the 'm7' file, the problem is pushing the 'su' file to the device to make the root permanent.
I do get the # symbol when in ADB Shell but only after changing m7 on the device. As i cannot complete the whole rooting process the # is not there permanently and it returns to the $ symbol.
Thanks for the reply, i will try and do it using a terminal on the device. Do you not need root access to use a terminal app?
I'm having the same issue. When I input exit it stucks into that loop and then I got to ctrl+c, and of course the root does not stick
From that point forward I can't do anything else...
If someone overcome the problem please post.
I just used this app to root a zte blade with a new greek stock rom:
http://forum.xda-developers.com/showthread.php?t=803682
Seems to work for almost all devices and in first post have some info about root levels and links to a workaround for devices that have some lock which prevents the full rooting.
I didn't tried anythink cause the rooting process was successful, but you can try this app and if still have problems try to follow the instructions given.
Good luck.
If you have your mobile rooted can you just use this commands:
cd /data/local/bin/
chmod 755 flash_image
flash_image recovery /sdcard/recovery-clockwork-x.x.x.x-click.img
to perform a recovery flash? Without using the su command?
I don't remember if I tried it, but, if it works I recommend using Androot for rooting the device, it worked for me(checked by Root Checker ).
I'm mentioning this just because you recommended the SuperOneClick app.
Update:
For all trying to get thing done, follow the instructions on 1Click modified by tenis and flash the latest cyanogenmod.
It worked!!!
I got it to work using androot. Cm7 is awesome
Sent from my HTC click using XDA App
exit command in adb seems to lock up
like omgsufc, I also reach this stage and can see the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(a db),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt ),3003(inet)
Again, like omgsufc, when I issue the command:
# exit
ADB shell seems to go into some kind of loop. Pressing ctrl-c or ctrl-d also give the same results. I thus can't go to the next stage. Any help or clues would be greatly appreciated.
I'm on Ubuntu 11.04.
TIA for any help.
Finally got it to work
No matter what I did, rooting using m7 just didn't work for me (Ubuntu 11.04). Running 'while ./m7 ; do : ; done' got me temporarily rooted as issuing 'id' shows me at 'uid=0(root)'. However, issuing 'exit' just left me in a long loop in the terminal from which it never recovers, and hence I could not complete the root process this way.
So I tried androot, which appeared to root me right away. Issuing 'su' in Android Terminal worked, and doing the same in ADB Shell also gets me to the # prompt. However, issuing the 'flash_image recovery' failed no matter what I did. I tried ROM Manager after this initial androot root: it gives me a success message after flashing ClockworkMod recovery, but when I reboot into recovery it just fails. Fastboot also failed consistently.
Finally, when I tried Terminal Emulator to get root access by issuing the command 'su', it says permission denied, even though Terminal Emulator gave me root access.
So... I unrooted Androot. Again trying to root using m7 I got the same problems as before.
I didn't bother trying flash_image or fastboot and instead tried rooting with androot. After doing so, this time Terminal Emulator allowed root access, which gave me some hope.
So I pulled out ROM Manager again, and woot! My Tattoo is on CyanogenMod 7 and am I a happy camper! I like what Cyanogen has given us: ADW Launcher is as good for me as Sense ever was... actually it's better. And finally I get to use all the new apps I've been wanting to use but wouldn't run on Android 1.6.
So thank you Cyanogen, thank you xda-developers, particularly KalimochoAz, thank you Koushik Dutta for ROM Manager, and thank you, whorever developed androot!
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
rydinsmoothx said:
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
Click to expand...
Click to collapse
Not gonna happen unless you can get into recovery or have the special usb cable to throw your device into fastboot (search the unbricking thread for more information on that). If you get lucky and can fix it + revert to stock, I would not install cm7 again until doing so is more noob friendly and forgiving.
The issues people are having with installing cm7 and severely screwing up their kindle are pretty epidemic due to the issues with recovery for those that don't prepare ahead of time for the possibility of disaster. The maintainer should really either close it out for now to the public or make the disclaimer much larger.
I have the same error. This is end. Only Factory Cable can help you but even with this cable I'm not sure what you can restore it.
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
rydinsmoothx said:
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
Click to expand...
Click to collapse
Operate how? Also, please don't double post in 2 threads.
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
rydinsmoothx said:
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
Click to expand...
Click to collapse
Could be a bit more explicit. Boots as in "yay, i see a logo and can't use my device beyond a paperweight that displays the cm7 logo" or boots as in "yay, i can use my device like normal and it's not bricked or malfunctioning"
Anyways, if you actually have root privileges and can mount system in read/write, get the sh binary out of the CM7 download by unzipping it or whatever and copy it over, making sure to match the owner/group and permissions that the other things in the /system/bin directory have. Since I'm guessing you're not command line savvy, I recommend doing this in root explorer or buying it if you do not have it.
Also, many of us do not own kindles and a larger % are also not running cm7 on their kindle so saying "i ran some random script that I won't say what it does and where I found it" does not help your situation either as far as getting a helpful answer.
Can you type ADB DEVICES at your command line and get a device? What about fastboot? Can you get devices to show there while at the command line?If yes, I am sure you can flash the CWM recovery to get ADB, then follow the steps to get back to stock...Dont blame me though if it doesnt work
I got the script script from someone in the cm7 thread, its supposed to opitimize the ram usage thus making the rom more smooth. He said it worked for him so I gave it a shot. I think it unrooted my kindle because I can't gain root access with root explorer. My devices shows up in adb devices but since I can't use adb shell I can't enable the fast boot.
I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.S
Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.
Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)
Poesini said:
Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)
Click to expand...
Click to collapse
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW. Once that is done, make sure the permissions are set to 0644, or rw-r--r-- & check the ownership to make certain the owner & group are both set to "Root". If you do not work on the "live" build.prop, then copy the edited build.prop to the root folder (/) first, then check permissions or change them using adb chown & chmod commands as required.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.
chratcliff said:
Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.
Click to expand...
Click to collapse
Glad to get you pointed in the right direction. This is what XDA used to be. How I learned anything at all. I am a mechanical engineer, not a software or hardware guy. Just a guy that will not give up on something broken.
It's all about taking little queues from here & there & then trying to assemble parts of different things into accomplishing what it is you are working on. All of this was based on things I tried or read in the past, working to root devices like the Xoom, etc... After reading about the exploit we had applied (what it is & how it works, some of which was beyond me), I was able to surmise that the exploit we used was still there as was the ability to access root permission, but that the tablet had "forgotten" we had root access rights because of the wipe. We just had to use adb to give it the files "memory" of our access to root & the permission to use them, in essence, tell it what we wanted. Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done. We need to provide that for it's brilliance to become useful.
As mentioned above, I highly recommend modding the build.prop & re-flashing the update.bin to have a clean slate.
GSLEON3 said:
Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done.
Click to expand...
Click to collapse
This is the damned truth never better spoken lol
Sent from my SPH-L900 using xda app-developers app
GSLEON3 said:
Ahhhhh.... XDA! The thrill of it all, you desperately want something now, you're a smart guy, you can do it & nothing beats that feeling of your sphincter tightening up, your heart racing, as you wait for that device to reboot....wait.....maybe another minute.....okay....crap... what do I do now? I love that feeling! I mean YOLO. Livin' dangerous dog, lol... Okay, I "bricked my device on PURPOSE, since there is a Play Store script in a ceertain tool that seems to be broken, or is missing information from the instructions, such as safestrap, or something.... That part I haven't figured out. I asked the creator to take a look at what he did & in the mean time, this should get you fixed up. It is actually much easier is you were not panicked to the point of factory resetting, but either way, the info below will get you sorted out.
I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.
Click to expand...
Click to collapse
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?
TOM XIE said:
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?
Click to expand...
Click to collapse
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?
GSLEON3 said:
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?
Click to expand...
Click to collapse
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.
Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....
TOM XIE said:
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.
Click to expand...
Click to collapse
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.
scx110a said:
Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....
Click to expand...
Click to collapse
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.
GSLEON3 said:
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.
Click to expand...
Click to collapse
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.
TOM XIE said:
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.
Click to expand...
Click to collapse
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.
GSLEON3 said:
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.
Click to expand...
Click to collapse
Hope you good luck.... That's really a complex thing since Amazon did so many changes to the DownloadProvider....
May ask you a question? plz
GSLEON3 said:
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.
Click to expand...
Click to collapse
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english
cjdfyd2 said:
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english
Click to expand...
Click to collapse
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.
GSLEON3 said:
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
(still can't post links)
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.
Click to expand...
Click to collapse
Tried using this method after the installation of gapps failed due to system directory being full (1gb)... I already gave up on this device until I saw this... Many Thanks! :highfive:
Thanks your answer and happy new year, i was wonder if could you help me?
GSLEON3 said:
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.
Click to expand...
Click to collapse
my device is kindle 7", i had followed step Cpasjuste's http://forum.xda-developers.com/showthread.php?t=2577826 and i delete these files
"/system/app/amazonmp3_4010410.apk" -> amazon mp3 ..
"/system/app/Email_310006810.apk" -> email app, replaced by gmail which is currently broken !
"/system/app/Photos_7016610.apk" -> photos app
"/system/app/OfficeSuiteViewer.apk" -> office ..
"/system/app/S2Service.apk" -> something to do with cellular i think
"/system/app/Launcher-release-signed_81224610.apk" -> amazon launcher
"/system/app/AmazonWebViewLib_1109110.apk" -> slik browser
"/system/app/com.amazon.cloud9-platform_38038110.apk" -> amazon cloud/sync
and flashing he's gapps file. and then my device is bricked. it's shown grey kindle fire logo only, so i reboot many times but still shown kindle fire logo only.
So i install ubuntu my laptop, and follow your step jcase's file download on my computer.
but i don't know how next step? how open "su" file? by sdk? work on window os? or linux os? sorry for many question plz help me..and happy new year
Hello,
My kindle is bootlooping on the grey kindle and orange fire logo. This is a HDX 7.
I rooted, went a bit crazy with uninstalling kindle bloatware, screen went black, thought factory reset would do the trick, end up in bootloop.
My computer recognizes the kindle so what should I do?