Related
So I'm booting Honeycomb off SD and all was fine and dandy. I got Market setup and all was well.
Well I decided to get a little adventurous thinking there wasn't much to lose and decided to push the system folder for all the GApps in the Froyo walkthrough. Now my Nook just boot loops, each time displaying an activation screen with LogicPD Zoom2 then immediately rebooting.
I have an idea of what is wrong, its trying to run a Google activation when it boots up, but since its the wrong device is boot looping. What I'm looking for is what apk to take off the SD card and in what directory I would find it to get myself out of this pickle. I'm trying to avoid starting over with the Honeycomb build, but it wouldn't be the end of the world.
So I'm thinking it may be OneTimeInitilizer.apk but am realizing I can't access the partition on the SD card directly from Windows. Any ideas
Edit: I may be able to get adb shell for a few seconds before reboot if that helps, I may be able to queue up the commands necessary and get them off in time.
Edit 2: Tried my (most likely wrong) attempt at the above idea. Created a batch file to mount as rw and then run adb uninstall /system/app/OneTimeInitializer.apk but it never worked. Either gave me Failure or "Error: Could not access the Package Manager. Is the system running?"
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
con247 said:
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
Click to expand...
Click to collapse
Just don't execute the program again after you have done it once, or it will boot loop the vivid to high hell. And you'll have to do a factory reset.
Sent from my HTC PH39100 using xda premium
Did that just happen to you? There is a 20 second timeout for a reason...
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
drewdatrip said:
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
If you know how to use adb on Mac or Linux you can just run the equivalent command one by one
Sent from my ADR6425LVW using XDA App
Code:
timeout /T 20
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb push zergRush /data/local/
adb shell chmod 755 /data/local/zergRush
adb shell /data/local/zergRush
adb wait-for-device
adb shell sleep 1
adb remount
adb shell mkdir /system/xbin
adb shell mount -t tmpfs none /system/xbin
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell cd /system/xbin
adb shell /system/xbin/busybox --install -s /system/xbin
adb install Superuser.apk
Does nothing different from the original scripts that were posted here a month ago.
Read my OP bud. I have downloaded all of the ones posted in your Vivid section and made sure. This one stores the root to a ramdisk that lasts until a reboot instead of /system rw mount going away after a short time.
I had a problem pushing this to the phone at first. Then I made sure the screen didnt time out and everything worked fine for me....just a little FYI incase someone runs into this problem as well.
Thanks
Didn't work for me.
I followed the instructions to the letter, and when I ran the batch file, there was no 20-second wait; it started immediately. It found the phone, went through the "sending speedbots" or whatever, and then rebooted the phone. It then re-ran ADB with "wait-for-phone" and the phone got stuck in a bootloop. I kept it connected to the PC and did a battery pull, and as the Beats Audio logo came up during boot, the command window on my PC flashed some more text and then closed. I let the phone completely boot and tried to run Titanium Backup and I get an error indicating it doesn't have root access. Any thoughts?
BTW - running Windows XP on a Dell Optiplex 755 with 4GB of RAM.
UPDATE - I tried performing the whole process again, and it ran for about 10 seocnds then just closed. So, I tried again, and it went through the process, up to rebooting my phone and indicating "wait-for-device," but the phone never completely shut down; it hung at that shutdown point where the entire screen is black but you can see a bit of lighting. So I did another battery pull and turned the phone on again, and after about 15 seconds, the command window scrolled a bunch more stuff and then closed and the phone continued to boot. It did manage to boot this time without a battery pull and no loops, and SU is there, but when I run Titanium Backup, I still get a "phone not rooted" error.
Looks like I'm waiting for perm root. Thanks for your work though. I'm glad it worked for others. Viva la Android!!!!
FYI: I did disable bloatware using a script, within the same command prompt window right after achieving temporary root.
The bloatware APPS and widgets remain disabled even after full reboots, including a battery pull.
I'm very grateful to temporary root, since it allows to disable most of the pre-installed bloatware.
Went from bad to worse.
I ran this on my phone last night, and even though it didn't temp root my phone, it still ran fine for the rest of the night and all day today. I decided to reboot the phone before I went to bed and now I am stuck in some kind of loop. The phone actually boots to the lock screen, and I can unlock it, but some of the icons on my homescreen don't load and the phone becomes unresponsive after about 10 seconds and then reboots. It's done this about 10 times and a battery pull does not resolve the issue. Help?
Have you tried a factory reset ? After that it may allow you to run the temp root. At least that is what happened once when I tried it.
Well through trial and error, I have found out several things...
1. The temp root that comes with the Rezound Clean Tool is the only temp root tool I can get to work.
2. Even if you have BT turned on before using the Rezound Clean Tool, turning it off permanently disables it until a reboot is done.
3. It is common for the Rezound to suddenly start boot looping, even if you haven't done any rooting or anything. This is caused by the connection type in Phone Properties randomly changing to a type that is incompatible with the Verizon SIM. (Google search "rezound boot loop" and you'll find the fix quite easily.) Also, removing the battery cover may disable the antenna but only a SIM-less boot will stop the boot looping so that the communication type can be set back to what it should be.
4. I still love this phone. It is the best phone on the market today; it has the fastest processor available from any carrier and has the most internal memory of phones that allows for removeable storage.
Thanks to all the devs for their hard work - I can't wait for perm root and custom ROMs!!!!
I'm just sayin' I hope that we get to see some love and get the CM9 rom for the OB. I would really like to get ICS before the middle of next year. Is there somewhere we can put in some kind of request? or is there a way to use an existing CM9 build to port it to the OB using something from a CM7 build? I've had the phone for about 5 months and getting tired of running 2.2 Froyo just still debating whether to take the plunge and root and put on CM7 or wait it out a little longer. I really have never messed with an android phone before but I read alot on the forum and it seems relatively easy to get the CM7 on there just afraid to root and lose my warranty and something break lol.
Just hack away, don't worry about your warranty. You might get your phone stuck in a bootloop, i've done that several times already, lol. It sucks when it happens, but you can always connect it to your windows pc and restore it to factory settings, unrooted and everything. No one will ever know your phone was rooted
And just to add something, if you can install Android SDK on your computer, you can use ADB Reboot Recovery (if you put recovery on your phone of course). It save me great time.
Sent from my LG-P970 using xda premium
how do u restore the phone? if I know I can unroot it and it won't affect my warrenty ill do it lol I have v10a and have never been able to update higher then that. do I use gingerbreak and the app says it can unroot? like I said if I can unroot it and keep warrenty ill do it
Sent from my LG-P970g using xda premium
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
xantaro said:
I got the EU Version of 10c rootet with this method:
1. Download and start SuperoneClick 1.9.5, click Shell Root
2. When it hangs up on a black CMD windows, close this Window. (You should have Shell Root now)
3. Unpack the attached File in your ADB Folder.
4. open a Command Prompt and enter "adb push su /tmp/" & adb push superuser.apk /tmp/"
5. Type "adb shell" ( When Shellroot worked, you should se a "#" on the shell
6. Enter the following commands in shell:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
7. The Phone will now reboot, after reboot it´s rooted again
Click to expand...
Click to collapse
hulkhaugen said:
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
Click to expand...
Click to collapse
What Sobralobo said is that just installing Android SDK (Search Google and you get more thousands of tutorials to install SDK and everything you need. Even in O Black section I think there is one with Black drivers and all. Maybe is this one.) you can use "adb reboot recovery" when your Black is in a bootloop or whatever, then you just flash/restore and you are done way faster than reflashing stock firmware. And in certain occasions (for example when you have a certain ROM and you try to flash a modded file in flashable zip that breaks it, you can just flash your ROM without wipe just to fix it and you lose nothing).
PS: You don't even need SDK. There are standalone adb packages, and with LG Black drivers, you can do the same.
This is needed when you mess up with the phone testing all the freaking day like I used to and many others do now.
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
hulkhaugen said:
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
Click to expand...
Click to collapse
Well, not directly related to nandroid backups. Just do "adb reboot recovery" (without the "") when you are in trouble. Depending on the situation you will have to input that many times (up arrow and enter fast and many times) if it's bootlooping to find the proper moment when the phone actually receives the command, but it's easy. Once in recovery, you do what you need to do.
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
hulkhaugen said:
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
Click to expand...
Click to collapse
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
antonio1475 said:
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
Click to expand...
Click to collapse
It won't work with adb reboot recovery,I've tried it and failed,won't detect the phone
At least,in my case, it happened when i tried to do a nandroid restore from cm7 to stock (v10a, wiped)
Sent from my heart into yours
So last night, I was beta testing a ROM. After playing with it for a while, decided to go back to my previous setup and work on something. I rebooted into TWRP, wiped my Dalvik Cache, data, cache, and system partitions, and tried to flash the nandroid of Kinology I had been running before testing the beta ROM. I rebooted... only to discover that my Kindle wouldn't boot past the 2nd bootloader.
I thought, "okay, no biggie, I can fix this. I tried wiping and then flashing a couple of other ROMs I had on my SD card. Didn't work. I rebooted the bootloader and flashed a trio of images I had on my hard drive via fastboot. Nope. I tried sideloading CM10.2. Still nope. I tried mounting USB and pushing a ROM to my SD card and flashing from there. Again, no (anyone noticing a pattern?).
No matter what I do, I can't flash anything or get anything to transfer over to my device.
Help!!
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering. "adb logcat" doesn't work. It only shows "-waiting for device-". I tried flashing CM11 this morning, but the install failed. I also tried re-flashing your ROM again this morning, but same result. I've got TWRP 2.6.0.0. I've been meaning to flash the latest one from @Hashcode, but it slips my mind every time I think of it.
Something weird: whenever I push anything to the device over ADB, I push it to the SD card. But when I run "ls /sdcard/" in ADB shell, there's nothing there (even though it says it has been successfully pushed).
EDIT: Okay, I flashed the latest version of TWRP (2.6.3.1). I flashed CM11, and it reported that the flash was sucessful. But when I rebooted... nope.
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Ph0enix_216 said:
No matter what I do, I can't flash anything or get anything to transfer over to my device. Help!!
Click to expand...
Click to collapse
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
stunts513 said:
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The init.RC scripts are still there, no matter how much I wipe in TWRP. I can see them using TWRPs file explorer. I haven't tried flashing the boot.img, I will try that. As for ADB, I'm using it on Windows 8, of all things.
LinearEquation said:
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
Click to expand...
Click to collapse
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
UPDATE
Okay, I tried re-installing CM10.2, and then flashing the boot.img from it via fastboot. Still no dice.
Is there any hope of recovering from this? It's been longer than a year, so I don't think Amazon will simply switch it out under warranty.
Agh, I was going to ask hashcode about it on the irc earlier and I forgot about it because my friend asked me to fix his pc...
Also remind me to slap this phone's spell check. It took me way longer to write the previous statement than it should have.
Edit: he's still in there but I think he's afk right now.
Sent from my LG-P769 using xda app-developers app
Ph0enix_216 said:
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
Click to expand...
Click to collapse
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was gonna suggest to flash CM10.2 first and then move up to CM11 because that was the route those with this problem had to go (4.3 then 4.4.) Restoring CM11 right off the bat did not seem to work for some reason. That's why I keep a 4.3 nandroid in TWRP, for just such a case. But I see you tried that.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird, because I wiped then tried to restore my Kinology nandroid. Am I looking at an irreparable brick, or do I want to look into investing in a new tablet?
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
stunts513 said:
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Checked everything. Wiped it all. Pushed a ROM via ADB. Not working.
I did some exploring with TWRP's built in file explorer. Despite wiping internal storage, I can still see some things I had on there previously. At the root of my device, however, I can also see this:
Code:
boot
cache
data
dev
efs
etc
license
proc
recovery
res
root
sbin
sdcard
supersu
sys
system
tmp
vendor
default.prop
file_contevts
fstab.bowser
fstab.goldfish
init
init.rc
property_contexts
seapp contexts
sepolicy
ueventd.bowser.rc
ueventd.goldfish.rc
ueventd.rc
I may be mistaken, but isn't that some of Firefox OS's stuff? The init.rc files you were talking about? It all may just mean nothing. Also, all my SD contents seem to be preserved in "/data/media/". I tried flashing CM11 from there as well. The flash was successful, but at boot... nada.
Still, thank you all for trying
Umm sorry I'm a little late to the party... Or funeral(if we cant fix your kindle) I was testing stunt's FireFox OS too and after testing I flashed back to my CM11 back up just fine, why not use the system image restore tool in the development section (minimize error, the tool is 99.9% fool proof) bailed me out multiple times when I thought my kindle was a goner(i know you manually flashed images. But why not try a tool?), and I have a theory... Stunt PMd me instructions on how to get the kindle to pick up/read the SD card I didn't try implementing the code because I'm not that techy but did you try it? What if the solution messed with your internal SD card since Firefox OS and Android Have their differences? Or something went wrong will modifying the commands stunts gave you?
And no...I'm not trying to insult Stunt's work or defame it, nothing is perfect and anything is possible so sorry if my response seems a bit disrespectful to the devs work.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
I still think this has something to do with selinux... I would know more if you had a serial hookup to the kindles motherboard but I don't even have that, if I had some kernel output it would be useful... Those files you saw that I mentioned aren't Firefox OS specific, they are Linux specific, they are going to always appear there because they are loaded from the initial ram disk in the boot.IMG, since android uses a Linux kernel you have init.rc files and such. Some of those directories are from recovery, the folders that should know appear empty I think are /data, /cache, /system and I can't remember the rest offhand. I will have to ask hashcode about this more tomorrow. I can think of something you might do from fastboot that might fix this but I don't know the specifics and it might wipe the boot loader, which wouldn't necessarily be bad as long as you reflash it before rebooting, but I'd like to avoid my idea because it seems rather risky, anyways I will ask about this tomorrow, so don't look into my concept idea....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
stunts513 said:
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
Click to expand...
Click to collapse
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Ph0enix_216 said:
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Click to expand...
Click to collapse
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
SUCESS!!!
stunts513 said:
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
Click to expand...
Click to collapse
SUCESS!!! I did what you said and formated the data partition, and I was able to successfully push CM11 to my Kindle. I flashed it, it reported the flash as successful, and I rebooted.. I was greeted by new CM11 boot animation (right now, it's one of the most beautiful things I've ever seen.
Thank you to everyone who responded to this thread. It's nice to know that there are people nice enough out there to take the time and help someone in need.
Some questions though:
1.) With this SELinux or whatever, can I still switch ROMs as easily as I did before? Or am I now limited to CM11 and such?
2.) What exactly happened? I've never had this happen before, where my /data partition derped out and TWRP wouldn't flash anything.
I'm not to familiar with how selinux works but from we hat I remember I think it was something like this. You had a recovery that I think may have supported selinux but I'm not positive about that. The kinology ROM you had on there had no selinux support in the kernel. My ROM has some selinux support in it since I based it on 4.3, and I have no idea what happened that messed it up after that, all I can tell based on what you had to do to fix it is that the xattributes for selinux were not getting cleared off the partition and for some reason the ROM's that could handle selinux didn't seem to like it either. If you want to run kinology again you may need to downgrade twrp so you can reformat the partition again so it reformats without selinux but I'm a bit confused on this myself, this isn't my best field in computers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I believe I habe the kfsowi model. it is 11.3.1.0 it is rooted and I am wanting to factory reset it but I dont have a factory cable. just a normal usb cable that I've been using adb to transfer and even instlal some files because through tweaking it, it lead to a missing status bar in which i change the qmenu = to 0 and 1 or whatever in build.prop but no matter what it doesnt keep the status bar active at all times like it should be. it is non existent until i click on an app in apex, adw or any launcher ive tried then it flashes and disappears. during this flash it is not usable no matter how fast i click it.
also a small issue it has is ever reboot, it says kindle is upgrading but it is not upgrading at all because i have tried to click check now in settings to check for updates but every time it says update failed. next after that message it says starting applications for about 20 seconds. long bootup. i have probably messed with tweak i shouldnt have with pimp my rom and also android tweaker 2 and pro before it became 2. so the status bar is non existent. sucks cause cant even get facebook notifications lol.
i did factory reset it by the menu and also by using andromizer app to click recovery mode and do it that way.
(without status bar i been using all in one gestures but now recently i switched to using LMT.
this kindle has a few issues since i made it kinda as minimal as i could and probably uninstalled a couple things i shouldnt of lol like it only installs apps with adb install and adb install -r sometimes as well as through 1mobile market which is awesome. it will not sideload anything now because through uninstalling an extra deal or two i should of, it wont allow me to enable unknown sources installation through menus. if anyone knows a way to do this through terminal of linux that would be great
thanks to any help
or would there be any way to use the water beta without the cable and only using adb or any other steps. which to my understanding is the only rom so far. thanks
If you are rooted You should I think be able to run these commands from a terminal in Linux, if you meant a terminal on your kindle then take off the and shell in the commands I list to run.
Code:
adb shell
su
reboot bootloader
I think if you are rooted it will kick it into fastboot and you can restore without a cable.
Sent from my LG-P769 using Tapatalk
thanks for the quick reply. yeah i am speaking of terminal from debian/ubuntu. I enter those commands you give me and it is recognizing the device. With adb I can even push files to install since it is screwed up and I can't access the menu part for installing from unknown sources. that is the worst part of the few issues I have with it.
after I enter those commands it only reboots normally. it doesn't go into the bootloader. I can get it to go into recovery mode where I am able to just do a normal wipe of the device but that is about it.
just to make sure I understand this. with a fastboot cable and all it is a different method from just a normal "wipe and reset" isn't it? it is using an untouched .img or something to put back to actual FACTORY as if bought from store? cause the normal wipe and factory reset doesn't put back the items I uninstalled of course from system and what not.
also is this safe to do without a factory cable. I just haven't ever needed one before and even if there is an extra step or two I don't mind instead of waiting a week for a cable.
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
if you could do that that'd be awesome. thanks. I just read up about a locked bootloader but I've seen it's made some progress. I just need to be sure to not turn it into a drink coaster lol.
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
slixz85 said:
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
Click to expand...
Click to collapse
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
stunts513 said:
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
Click to expand...
Click to collapse
ok sounds like I need to find out if putting water on this without a fastboot cable is possible then