Related
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!!!!
My screen broke tonight enough to make it unusable, and I was offered in store exchange when I called B&N support. I am running CM7, and would like to know if it is possible to either restore to stock or wipe the hard drive to remove evidence of rooting before I send it back.
I managed to get into adb and read in another thread to try rm -r *, which is supposed to wipe everything, but I got a bunch of read only errors. It appears that the nook will now not boot into CM7 (which is good), but I fear that I haven't wiped it far enough to be safe from a chargeback. Any ADB wizards out there with some advice?
I think I have done it. I opened up a shell in adb, mounted /system as r/w, then did rm -r *. after a reboot it won't even boot into adb anymore. it comes on for about 4 seconds then shuts off immediately. I can't tell what is happening on the screen because of the damage, but i'm hoping it is enough that the folks who check returns at BN can't prove it was rooted.
What are you wanting it to boot into if you just deleted everything in the system partition?
Sent from my HERO200 using XDA App
I think he wanted it to not boot at all in preference to booting into CM7.
I'm pretty sure that if they looked beyond the broken screen they'd be able to determine that you've rooted it: Having no files but still a filesystem on /system is kinda suspicious, and I imagine that having CWM instead of the stock recovery would be something of a giveaway as well.
So for the last 7 hours i've been researching how to root/ install JB or another rom onto this brand new kindle i have running 10.2.3.
I've got ADB running and i've tried Sparkym3 and a few other root methods and i keep getting permission denied when i go to write fbmode or su
SO i'm at a loss, i'd really like to get this installed and working for my handicapped father's new kindle, its his xmas gift, and i know i'd prefer he be able to use google play and stuff.
Any help would be fantastic, this is really rattling my brain.
Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939
scubamike said:
Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939
Click to expand...
Click to collapse
The commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
^^^ Method i tried, and failed, wont allow remount, gives me permission denied, i didnt try Qemu at all.
If i could get access to play store i'd be fine keeping it on stock, i just want my dad to be able to use this thing with standard apps.
I think this method is strictly for the kindle fire HD and i'm trying to do it on a standard Kindle Fire.
Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz
yanzz said:
Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz
Click to expand...
Click to collapse
My device lets me punch in the echo command but once i hit mount or push i'll get permission denied so i'm at a loss myself. I hope one of these higher end techies can help us make this happen before Christmas time or my dads kindle stays stock :crying:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.
bodi524 said:
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.
Click to expand...
Click to collapse
I tried that last night, but it didn't work for me. Does anyone know if the .bin files from Amazon are flashable through fastboot... It would definitely be worth building/buying a factory cable if we could fastboot flash back to 10.2.1, root, and block ota updates.
Not to beat a dead horse but I am having the same trouble with Kindle Fire 2. Lost Root access last night when Amazon pushed 10.2.3. I tried to down-date to 10.2.1 but the .bin file keeps getting deleted from the kindleupdates folder after I press the update button in "settings-device-about". Unfortunately I learned about disabling automatic updates a little too late. Thank you in advance for helping us out. We are not worthy.
arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.
xiastro1ix said:
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.
Click to expand...
Click to collapse
I am willing to try the hack posted for the 8.9" bootloader.
However I want to know the restore process works first.
If someone will pull the partitions to restore, zip them and post them I will try the backup on my KindleFire2.
See Here:
http://forum.xda-developers.com/showthread.php?t=2032822
Mine is bricked as of now so trying to restore it won't harm it anymore that it already is.
Once we having a working restore I will try the bootloader crack....and in an exchange with
Hashcode he said he thinks the Original KF roms will then work (WITH SOME KERNEL CHANGES)
for the KindleFire2.
this thread
http://forum.xda-developers.com/showthread.php?t=2033297
claims that they've got root working on the current version, but I tried and it doesn't even recognize my device is plugged in. Several confirmations in that thread that people have it working though.
confrmed root access on 10.2.3
http://forum.xda-developers.com/showthread.php?t=2033297
Just completed hooray!
Now to replace ROM
well it claims its rooted and it has super user installed, but i still cant get past permission denied messages when trying to go ahead and get a new rom on it.
Not sure what to do here, i want to get google aps on it and i'll be fine, but i don't know what file explorer would be good for the stock rom that i can get through the amazon store :\
I'm actually not sure if it is rooted, the first method installed SU onto the phone, but i don't actually see the second portion processing the exploit, its getting permission denied aswell, the kindle has superuser on it, but now i'm completely lost, i still cant get it to do anything....
Edit- ALL DONE YAY
Got googleplay and 1mobile installed, just had to purchase ES file explorer and play around a bit
Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.
Trendy Ideology said:
Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.
Click to expand...
Click to collapse
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,
xiastro1ix said:
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,
Click to expand...
Click to collapse
I was trying to use the ADB drivers found here,
http://forum.xda-developers.com/showthread.php?t=1893838
but when installed they didn't say anything like that in the final step that showed me what was installed, it said amazon kindle somethingorother.
Device manager went from showing
Portable devices
|
_ Kindle
To now
Kindle Fire
|
_ Kindle
Installing the driver manually gets me something that looks like ADB Kindle Fire but now it doesn't show up in My Computer at all, and the root with restore
http://forum.xda-developers.com/showthread.php?t=1886460
doesn't "see" my kindle...
I'm rather lost.
Here's a log of as far as I've gotten so far:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (22.11.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
error: device not found
Waiting for device to show up again....
Going to copy files to it's place
/system/bin/sh: /data/local/tmp/busybox: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
It's only "Seeing" my kindle if I power it down, plug in the USB, and then it seems to "catch" it while it's booting up. And it remains caught until the tool lets go of it and then it goes to the lock screen as normal.
on this step
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
I get no restore option, probably because my kindle is in a booting state when this is all happening.
I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Deflection said:
I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Click to expand...
Click to collapse
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks
reyvaj said:
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks
Click to expand...
Click to collapse
There is a whole forum for kf1. Kf1 runs 6.something not 10.2...
Hi, i need help, i want root my kindle fire first generation 7 on 10.2.3_user_2313820 sw version, many thanks
Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.
kent13 said:
Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.
Click to expand...
Click to collapse
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot
samersh72 said:
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
Hi samersh72,
I have tried it before and didn't help. When I reboot the phone, the problem persists and the file still with 'OFF'. I don't know if it makes any differences, but I'm running those commands through adb, since I could not install any app. (I tried to push the apk file of terminal emulator to /syste/app/ but it crashes when I try to open it. I also tried to do it using Root Explorer.. Both cases, no success.)
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app