[Q] Sony Tablet ICS 4.0.3 - bricked it - Sony Tablet S

Hello,
I followed the instructions
in http://forum.xda-developers.com/showthread.php?t=1886310
to root my tablet.
I do it using Linux so I don't use the half automatic way.
I signed also the VpnFaker.apk
But it does not work, I got the error at the end, sometimes mentioned:
:~/Infos/android/SonyTabletICS4.03Root> adb shell am start -n com.android.vpndialogs/.Term
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does not exist.
I tried the same procedure again - no success and all my apps are gone.
Ok I thought - I do it back.
I copied the old system- and old app- back to system and app.
And that was it ...
The device does not start. It shows sony and after that the yellow to golden
animation which normally ends sometimes.
It does not end.
I can connect via adb on linux not on windows (I use it very rarely and the win 7 notebook
allowas says that the driver is not installed correctly )
I can't get the right to manipulate /data
using the while loop. I think I can't confirm the restore with the touchscreen.
I post this also in the thread http://forum.xda-developers.com/showthread.php?t=1886310
I don't know what to do now.
Greetings
Karsten

I think we have the same issue, in my case I can't fix it until Sony release a new update.
Can you post your recovery log?
Sent from my MB525 using xda app-developers app

karo said:
Hello,
I followed the instructions
in http://forum.xda-developers.com/showthread.php?t=1886310
to root my tablet.
I do it using Linux so I don't use the half automatic way.
I signed also the VpnFaker.apk
But it does not work, I got the error at the end, sometimes mentioned:
:~/Infos/android/SonyTabletICS4.03Root> adb shell am start -n com.android.vpndialogs/.Term
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does not exist.
I tried the same procedure again - no success and all my apps are gone.
Ok I thought - I do it back.
I copied the old system- and old app- back to system and app.
And that was it ...
The device does not start. It shows sony and after that the yellow to golden
animation which normally ends sometimes.
It does not end.
I can connect via adb on linux not on windows (I use it very rarely and the win 7 notebook
allowas says that the driver is not installed correctly )
I can't get the right to manipulate /data
using the while loop. I think I can't confirm the restore with the touchscreen.
I post this also in the thread http://forum.xda-developers.com/showthread.php?t=1886310
I don't know what to do now.
Greetings
Karsten
Click to expand...
Click to collapse
Factory RESET from recovery

I don't think so. if the problem is on /system directory, factory reset will not help.
Sent from my MB525 using xda app-developers app

_kyo_ said:
I don't think so. if the problem is on /system directory, factory reset will not help.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
I had to do factory reset when I was trying to root and it worked for me. I know your problem is worse unfortunately
Just thought it was worth a try in this case

of course it worth a try
Sent from my MB525 using xda app-developers app

adb logcat of bricked device
Hello,
the log get by adb logcat repeats after some time, so here
is only one part.
Since yesterday I try in /data/system - yes I could read it don't have permissions on app:
/data/local/tmp/busybox find . -type d -exec chmod 755 {} \;
/data/local/tmp/busybox find . -type f -exec chmod 644 {} \;
ups the log is to long you can find it under
zb42.de/logcat-2012-09-23-v2.txt using your browser
(sorry I'm not allowed to post a link to an external site)
there are three lines which shows where the logs repeat :
--------------------------------------------------
and from here it seems to repeat
-------------------------------------------------
hmm, now I have done a
/data/local/tmp/busybox find . -type d -exec chmod 777 {} \;
and the system starts but all applications vanished.
Puh, but it seems I'm back to the system.
Log shows still many errors, there is no app available,
Apps are shown on the Screen, but if I tap it
then it says: "App ist nicht installiert" (application is not installed)
I think my fault was that I copied back the system- directory so I have
destroyed the correct permissions on the file-system.
Can anybody give me a hint, how I should go further.
First goal would be a working system, second goal is
rooting
My goal of rooting was:
- curiousity (right word? Neugier in German) I've done it with Android 3
- correct the sdcard problem
update - device is rooted, I needed to start from factory defaults - then it works
Thanks
Karsten

dont think /system - I never touched it
no longer important, I can't delete this

Related

Samsung Galaxy 3 GT-i5800/i5801: Enable Live Wallpapers

Due to "high demand" here's a dedicated thread to explain howenable live wallpapers on Samsung i5800/i5801. You can find original tutorial by ali_alex here:
1) You need to root your i5800/i5801, you can find a tutorial here. An alternate method to root was described here
Video for the same see this : http://www.youtube.com/watch?v=cus0yaC5ayY
Hope OP doesn't mind just trying to help - thanks hari
2) Download and unrar "sdcard.rar" (attached to this thread) in your SD Card
3) Download Terminal Emulator from the market (http://www.androlib.com/android.application.jackpal-androidterm-zxnC.aspx)
4) Start terminal emulator from your i5800/i5801 and write (in orders):
Code:
su
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
cat /sdcard/LiveWallpapersPicker.apk > /system/app/LiveWallpapersPicker.apk
cat /sdcard/libRS.so > /system/lib/libRS.so
cat /sdcard/librs_jni.so > /system/lib/librs_jni.so
reboot
When you write "su" and press enter, terminal ask for root permission, give it
5) Once rebooted you can use live wallpapers
Thanks, it works fine. Very nice tutorial!
Sent from my GT-I5800 using Tapatalk
when i write su and press enter it says not found what to do?
Live wallpapers not working on a rooted phone
I've sucessfully rooted the phone using adb and the root.rar from the thread but I cant seem to enable live wallpapers.
Tried the manual transfer of files as well as adding the files in the update.zip file before rooting.
Here is a transcript of an adb session
Code:
C:\root>adb shell
$ su
su
# ls /system/app/LiveW*
ls /system/app/LiveW*
/system/app/LiveWallpapersPicker.apk
# ls /system/lib/librs*
ls /system/lib/librs*
/system/lib/librs_jni.so
# ls /system/lib/libR*
ls /system/lib/libR*
/system/lib/libRS.so
#
So, I know i have the files in the right locations. Now, what am I missing. The Live wallpapers option doesn't appear at all in the "Select Wallpaper from" picker along with "Gallery" and "Wallpaper gallery".
Would appreciate some help.
Cheers.
vj.vijay20 said:
when i write su and press enter it says not found what to do?
Click to expand...
Click to collapse
Root is required
It does work, but the best of them, like the Galactic Core, slows down the phone alot... it just cant handle most of the live wallpapers.
Guess theres a reason not to have them in the first place
hey buddy,
wen ever i prompt of live wallpapers, a msg pop ups "the application livewallpapers has stopped unexpectedly. please try again"
Plz help. hav already worked on this4 hours. dnt want my efforts to go waste.
got it working
Got live wallpapers working for my i5801. It was a problem with the owner/group settings.
Incase anyone else has the same problem do this.
su
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
chown root.root /system/app/LiveWallpapersPicker.apk
chown root.root /system/lib/librs_jni.so
chown root.root /system/lib/libRS.so
Click to expand...
Click to collapse
Cheers
LenZoid said:
So, I know i have the files in the right locations. Now, what am I missing. The Live wallpapers option doesn't appear at all in the "Select Wallpaper from" picker along with "Gallery" and "Wallpaper gallery".
Would appreciate some help.
Cheers.
Click to expand...
Click to collapse
Live wallpaper not working....
I have the files in the right locations. Now, what am I missing. The Live wallpapers option doesn't appear at all in the "Select Wallpaper from" picker along with "Gallery" and "Wallpaper gallery".
I've tried all the settings mentioned here....please help
Need your help urgently......real urgent....
Hi,
Need your help urgently......real urgent....
I had rooted my phone (samsung galaxy 3) to run live wallpaper, somehow that did not happen, i tried to root the phone again but now it is stuk on the Android System Recovery screen, giving me option to reboot the system / apply sdcard:update.zip....etc etc..
iv'e rebooted the phone multiple times...it is not starting ....please please please help me......
help...
when iwrite these code it shows "cannot create......:read only file system" what to do
I am also facing same problem as the one of the above user.I think that i have rooted my phone because when i type su i am granted special read write permission. when i type the cat & the rest of the command i get this read only error.
Pls help.
sonijd said:
Hi,
Need your help urgently......real urgent....
I had rooted my phone (samsung galaxy 3) to run live wallpaper, somehow that did not happen, i tried to root the phone again but now it is stuk on the Android System Recovery screen, giving me option to reboot the system / apply sdcard:update.zip....etc etc..
iv'e rebooted the phone multiple times...it is not starting ....please please please help me......
Click to expand...
Click to collapse
remove sd card and reboot... sorry for my english
Wallpapers works great! Thank you!
Friends from India
hi friends,
Even i couldn't get the Live Wallpapers in the First Go.With Same Error "Cannot Create ... : Read only file System"
but i guess the mistake is simple jus try typing as it is given even Caps,Spaces etc.
it worked for me.
And Thanks To the Admin for posting this it took me a little more than 5 hrs to figure out the correct file even after giving the links (there's a spl file for I5801 india) please try rooting through that.
Love this forum
I'm able 2 run first line but when i tried 2 execute 2nd line it gave me following error
cannot create /system it is a directory
wat is that special file i'm also from india plz rep me back 2 my email if possible send d file also my id is [email protected]
Rooting and installing the live wallpaper worked perfectly for me, although I had a little hard time typing the codes.
The only problem I face now is that my phone isn't coming as a storage device when I plug it in the USB. I tried the USB settings, Debugging etc in the phone. The PC detects it as "Samsung USB Composite Device". Any solutions to my problem?
Its probably a typo that causes the error. I suggest going to ur internet browser on your phone, to this website, and simply copy each kernal 1 line at a time.
also, I have enabled live wallpapers, and while its an amazing feature, i seem to have a problem, and that problem is that the phone switches off once in a day due to locking up and then restarts.
i have been at it for 5 god damn hours and nothing has happened....it jus keeps saying no such dir found....
its there u damn phone!!! look!!
what do i do to fix this....have read all the threads relating to live wallpapers....no luck!

[Q] [HCDR ROM 1.7] Market update

Hi,
Sorry for my English; I'm French people.
I have an HTC Tattoo with HCDR ROM 1.7 since one year. But with the patched market i can't have the new version of the market. I read lot of topic about the subject in this forum and the Frandroid forum but I not found a running issues.
Have you got a solution for my probem ?
Thaks a lot,
Florian
florianlyon
Dude, hey! I ran into same problem.
Here you go: http://forum.xda-developers.com/showthread.php?t=723255&page=66
read last messages in the thread, especially my posts
Hey !
Thanks for you answer. I have already read this posts but it's not work for me !
If you have successfully fix this problem please leave me the procedure and shell command.
Follow the URL and download original market:
http://www.mediafire.com/file/wrw9tdzhveoqvgh/Vendingtrue.apk
Then reboot your phone to recovery.
Start cmd in windows.
Go to C:\rtattoo folder (i presume u use 1-click root-rec too).
If necessary mount your phone's system partition as RW:
Code:
adb shell mount -o remount,rw system
And the main command u have to run here is:
Code:
adb push Vendingtrue.apk /system/app/Vending.apk
note: of course it's implied that Vendingtrue.apk should be in the same directory as adb or locate it in a different way if u want.
If push command executes successfully just restart your phone, if not - then, naturally, do some work around. U may even try running it under loaded Android, it may do the trick too (for example, once when i tried installing hosts file it worked).
The main idea, as u might have already guessed , is to replace Vending.apk. Then it will autoupdate itself at the first time u launch it.
Hope it helps, good luck, dude!
I have try this procedure when Android running but it was impossible to push the new Vending.apk even with the system partition mounted.
But in Recovery mode I could push the new apk.
But when I launch the market it not auto update and when I run
Code:
adb pull /system/app/Vending.apk
The Vending.apk size is 1158ko, as the vendingtrue.apk size is 1146ko.
So I conclude that the replacement was not performed.
Have you got a solution ?
Thanks a lot
Dude !
I retry and it's work !
My system partition was not mount correctly.
I launched the following command with my tattoo in recovery mode :
Code:
adb shell
mount /dev/block/mtdblock3 /system -o rw
ctrl+c (or exit)
adb push Vendingtrue.apk /system/app/Vending.apk
I reboot my tattoo and launch :
Code:
adb pull /system/app/Vending.apk
The size is 1146ko (YES my APK has successfully replace).
I ran the market, 5 minute after, it was up to date.
thank you very much for your precious help !
the new market is rubbish...too bug...too slow...get the old market...I have download the old market I can ensure you it's better than new

Safe Mode issue feedback

Hello all!
I realize that many many Android users have that issue and don't get any satisfying answer.
Let me introduce you my own experience. This may help and clear things up about Android safe mode.
It started one week ago when I got into a party and the barman threw lots of water at my friends and me. When I went to bed I didn't bother dry myself up, went straight to bed and slept.
When I woke up the next morning (with such a bad headache by the way ), my phone was acting really weird :
1 : it couldn't recognize my SIM card or any SIM card
2 : the little textbox "Safe Mode" had appeared
3 : My Volume up/Volume Down buttons weren't working anymore.
I rebooted the device several times, wondering why would it do that to me!! I googled that all day to understand what was happening to it.
All of the sudden, after a reboot, the Sim Card was recognized again and this problem was fixed. Yay!
Then, I tried all I could about the buttons (opened the device with youtube tutorial and a Torx screw driver T5) tried to clean the volume flex cable, dry it... Nothing to do.
The volume buttons still not responding, safe mode still here.
There are several reasons for safe mode to show itself :
-Holding a button while booting (depending on the device and manufacturer) : simply reboot the device to get back in normal mode.
-A previously downloaded and installed app is causing issues on the device (Android self protection) : you'll need to find that app and uninstall it to get back in normal mode.
-I ran into a forum where someone was explaing how changing one of his internal components that wasn't working anymore fixed his safe mode problem (mostly non responding buttons like my phone).
So I ordered a brand new volume flex cable for my HTC sensation and I am still wating for it (long delivery...) I'll let you know as soon as I replace the component if that has fixed it.
The problem is : in the meantime I just can't access non system apps (in other words : all origin apps, no others). I bought a smartphone to be able to do many more things on it than just call, text message or email...
So I found a solution about it (I am going to test it tonight and will let you know) :
You need to have a rooted device in order to install all apps that you need to run, even though Android is running under safe mode, into /system/apps location. This will "make believe" those apps are actually system apps and will force your device run them at boot.
How does this work?
You need to get ADB tool in order to push command shell to the device (because terminal emulator or other apps that ease root commands directly on the device can't be loaded... Thanks safe mode!!)
!!!!! Important !!!!!!! I haven't tested this myself yet but will tonight and will let you know on that thread, so watch it before doing anything you wouldn't understand.
from Adb terminal you'll need to get into the system partition and mount it as read and write :
adb shell
su
mount -o remount,rw /dev/null /system
give everyone permissions to write in that folder :
chmod 777 /system/app/
Then, you'll need to store the apks you need into your sdcard (wherever).
Then, copy all apps you need into the folder :
cp -a /sdcard/[pathtoyourapk/theapkyouwanttoinstall] /system/app/
reset the permissions on that folder :
chmod 755 /system/app/
mount -o remount,ro /dev/null /system
sync
Reboot the device :
reboot
You're done.
Don't hesitate correct me if I gave any wrong information, but trust me, I spent enough time on this problem to get self confident and write in here.
Thanks for your attention!
Regards!
Adding information
I tested it and it does work.
However I forgot something :
Once you've copied your apk into the system\app folder just chmod it with 644 :
chmod 644 /system/app/[yourapp.apk]
This will give the system and yourself access grant to the application.
There! =)

[HOWTO] Unbrick your device

This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
We really did need this excellent thank you very much!
jimyv said:
We really did need this excellent thank you very much!
Click to expand...
Click to collapse
I still don't know whether this works or not. There's no reason it shouldn't work, but you never actually know until you try.
Sent from my Nexus 7 using Tapatalk
Sorry for the dumb question, but when you say try those commands, where do you enter them?
Let's Note. Comback to 4rum.xda....
Big thank for your method, Senior r3pwn
dburns865 said:
Sorry for the dumb question, but when you say try those commands, where do you enter them?
Click to expand...
Click to collapse
I have the same question with you
wow
danhvt said:
I have the same question with you
Click to expand...
Click to collapse
I'm sorry guys but if you really need to ask this then you probably shouldn't have been modifying your devices in the first place http://forum.xda-developers.com/showthread.php?t=2786190
Fix Bricked
Sorry, Im slightly confused, how are we able to fix the device with ADB if it is bricked? Mine will not get past the white "Kindle Fire" page, any ideas?
i will test this tonight. Bricked my kindle hdx but my wife has a working one so hoping if this doesn't fix mine i can somehow use her system files to fix mine.
thanks and will update tonight!
It worked for me
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
For the 8.9" HDX, they are posted at
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks dude, it worked for me. I mistakenly formated data after wiping system so I stuck in safestrap recovery. I transfered a stock Rom through ADB but It failed while flashing... because there was some kinda problem with Cache partition... so i tried your method and it worked... but i made a little change in last Commands... I gave it "EXIT" command only 1 time and did not give the command "ADB reboot Recovery"... I recommend you guys to manually boot to safestrap recovery after quitting CMD.... Ahhh my device is Kindle Fire HDX 7"
root not required?
Thanks, r3pwn, this works well. Nice, easy instructions that should be instructive to anybody messing with their device.
This helped me after a botched update to newer Amazon firmware. Quick question though: It seems like you don't really need to be root / use su to do these steps. I had lost su in that update but was able to execute the rest of the adb commands without root. I guess that should be the same for anyone who doesn't have root, right?
scaftogy said:
Thanks, r3pwn, this works well. Nice, easy instructions that should be instructive to anybody messing with their device.
This helped me after a botched update to newer Amazon firmware. Quick question though: It seems like you don't really need to be root / use su to do these steps. I had lost su in that update but was able to execute the rest of the adb commands without root. I guess that should be the same for anyone who doesn't have root, right?
Click to expand...
Click to collapse
Do you mean I can use this way to downgrade my firmware?
Thanks. but i have question now.
does it work on 4.5.2? as my friend remove the framework-res, and get it bricked T_T.
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
hi,
any glue what went wrong with a permission denied? everything in the adb shell session was ok, but adb push says (after several minutes!):
Code:
D:\adb_fastboot>adb push update-kindle-13.3.1.0_user_310079820.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.3.1.0_user_310079820.bin' to '/cache/kindleupdate.bin': Permission denied
sn123py said:
hi,
any glue what went wrong with a permission denied? everything in the adb shell session was ok, but adb push says (after several minutes!):
Code:
D:\adb_fastboot>adb push update-kindle-13.3.1.0_user_310079820.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.3.1.0_user_310079820.bin' to '/cache/kindleupdate.bin': Permission denied
Click to expand...
Click to collapse
No, sorry, I don't even have this device. There are newer, better ways to unbrick now.
I think trying to find eMMC pointer
i have tried this.. but when rebooting it takes me back to recovery menu with 2 options.
1. reboot
2.reset
whichever i chose, still takes me back to boot loop (animated logo)
any ideas?
does this method require TWRP? As i cant get this working..
Ali Ejea Mc said:
Thanks dude, it worked for me. I mistakenly formated data after wiping system so I stuck in safestrap recovery. I transfered a stock Rom through ADB but It failed while flashing... because there was some kinda problem with Cache partition... so i tried your method and it worked... but i made a little change in last Commands... I gave it "EXIT" command only 1 time and did not give the command "ADB reboot Recovery"... I recommend you guys to manually boot to safestrap recovery after quitting CMD.... Ahhh my device is Kindle Fire HDX 7"
Click to expand...
Click to collapse
I was trying to root my Kindle fire HDX 7 for android apps and google apps on it. it was successfully rooted and google play services working on it perfectly. Than suddenly google play stop working on it. but games installed on it working properly. Then i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC and in device manager only shows connectivity as MTP USB device. But no device show in my computer. Snapshot attached. Please assist any solution. I am not familiar with developer language. So please assist step by step.. Thanks
My Kindle fire HDX 7 i think bricked any solution?
I was trying to root my Kindle fire HDX 7 for android apps and google apps on it. it was successfully rooted and google play services working on it perfectly. Than suddenly google play stop working on it. but games installed on it working properly. Then i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC and in device manager only shows connectivity as MTP USB device. But no device show in my computer. Snapshot attached. Please assist any solution. I am not familiar with these developer language. So please assist step by step.. I tried below command but su Permission denied.

[Q] Used Rooted Kindle. Where to start with installing new rom?

I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Aftermath__ said:
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Click to expand...
Click to collapse
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Davey126 said:
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Click to expand...
Click to collapse
Thanks, also he said something about changing device name in build.prop Is it important?
Aftermath__ said:
Thanks, also he said something about changing device name in build.prop Is it important?
Click to expand...
Click to collapse
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Davey126 said:
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Click to expand...
Click to collapse
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Aftermath__ said:
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Click to expand...
Click to collapse
You're done. Recovery is almost impossible.
Davey126 said:
You're done. Recovery is almost impossible.
Click to expand...
Click to collapse
Not necessarily...
@Aftermath__: Can you gain adb access?
EncryptedCurse said:
Not necessarily...
@Aftermath__: Can you gain adb access?
Click to expand...
Click to collapse
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Aftermath__ said:
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Click to expand...
Click to collapse
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
EncryptedCurse said:
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
Click to expand...
Click to collapse
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Aftermath__ said:
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Click to expand...
Click to collapse
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
EncryptedCurse said:
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Aftermath__ said:
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Click to expand...
Click to collapse
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
It worked. Thank you so much for your help.
Aftermath__ said:
It worked. Thank you so much for your help.
Click to expand...
Click to collapse
Glad you are able to fix the problem. Props to EncryptedCurse for picking up the ball and pointing you in the right direction. Thanks also to draxie for posting a solution. Not many devices live through a soft brick. Well done.
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Aftermath__ said:
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Click to expand...
Click to collapse
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Davey126 said:
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Click to expand...
Click to collapse
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
- download 3.2.5 here; print upgrade instructions
Click to expand...
Click to collapse
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Aftermath__ said:
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Click to expand...
Click to collapse
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Davey126 said:
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Click to expand...
Click to collapse
I tried and i can't do factory reset because of the same issue as with the upgrade/downgrade. I guess the reason is that I flashed this recovery and I really shouldn't.

Categories

Resources