Please help! Accidentally did a wipe /system in TWRP and now get the message "exec '/system/bin/sh' failed: No such file or directory". How can this be a fix?
Having no experience with the fire, my guess would be to use the USB mount in twrp put on cm7 flash it.
Sent from my Full Android on Bravo using XDA App
adbirdie said:
Having no experience with the fire, my guess would be to use the USB mount in twrp put on cm7 flash it.
Sent from my Full Android on Bravo using XDA App
Click to expand...
Click to collapse
Now I have nothing else works except ADB. I tried to copy the system dir by
adb push "D:\sdf\system" /sytem
but in result received message:
push: D:\sdf\system/app/Windowshop.apk -> /sytem/app/Windowshop.apk
failed to copy 'D:\sdf\system/app/Windowshop.apk' to '/sytem/app/Windowshop.apk'
: No such file or directory
What am I doing wrong?
You need to flash a zip in recovery try cm7
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
You need to flash a zip in recovery try cm7
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
With TWRP I flashed stock firmware, then decided to wipe everything. So now I have no recovery. Just sign on the screen "Kindle fire"
When I try to do adb shell I get the message "exec '/ system / bin / sh' failed: No such file or directory"
Sorry for my poor English.
If you flashed stock firmware with TWRP, then can you just not do that again?
I didnt think wiping system wiped recovery.... In fact, im sure it doesnt as I wiped system yesterday when I flashed CM7.
About the adb push thing not working. Not tried, but does ADB recognise windows formatted paths? Seems like it doesnt. Move what you are trying to copy into the adb directory and try again.
Oh lord stock overwrites the recovery. Looks like your device is broken permanently, the same thing happened to me and my first kindle. Unless you can get yourself a factory cable you are going to need to get a new one
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
Oh lord stock overwrites the recovery. Looks like your device is broken permanently, the same thing happened to me and my first kindle. Unless you can get yourself a factory cable you are going to need to get a new one
Click to expand...
Click to collapse
Sad
factory cable? Where I can get it? Can be solder?
Im confused, sorry. If you flash Stock using TWRP, and this means you lose recovery, how can you then do a system wipe using TWRP?
alchemyst said:
Im confused, sorry. If you flash Stock using TWRP, and this means you lose recovery, how can you then do a system wipe using TWRP?
Click to expand...
Click to collapse
you can wipe system...but you can't flash stock firmware, as it will install stock recovery, then you lose function over your TWRP recovery, hence the whole process halt!
ck_looi said:
you can wipe system...but you can't flash stock firmware, as it will install stock recovery, then you lose function over your TWRP recovery, hence the whole process halt!
Click to expand...
Click to collapse
Maybe you can flash twrp with the fastboot command. If you still get recognized by adb devices you are not totally lost.
Sent from my SGH-I777 using Tapatalk
warren2781 said:
Maybe you can flash twrp with the fastboot command. If you still get recognized by adb devices you are not totally lost.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
That was my thought too. Could you use idme to set the boot mode to fastboot then use that to flash twrp and firefirefire? Even if idme isn't available, you can adb push it from a computer.
ttabbal said:
That was my thought too. Could you use idme to set the boot mode to fastboot then use that to flash twrp and firefirefire? Even if idme isn't available, you can adb push it from a computer.
Click to expand...
Click to collapse
when i try "adb shell" i get message "exec '/system/bin/sh' failed: No such file or directory"'.
ttabbal said:
Even if idme isn't available, you can adb push it from a computer.
Click to expand...
Click to collapse
What exactly should I push?
when your fire boots to the "kindle fire" screen connect it to comp and try running the "fastboot devices" command and see if it will recognize it, if it does then you are ok we can fix it if. make sure you are in <your path to sdk>/platform-tools to try the fastboot commands.
I had this problem with my first kindle. Afaik there's no way to get into fastboot without a factory cable in the current state that it's in. He's missing the sh binary that actually lets you go into the shell. He can't push to the system because he doesn't have the su binary so he cannot remount. There's no way to push files to a PATH location as they are all read only unless you're root. He needs a factory cable or he's screwed.
As for the cable itself, if you Google tbh Motorola factory cable you'll find it. You can also make one from an existing cable, just google around for a guide
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
I had this problem with my first kindle. Afaik there's no way to get into fastboot without a factory cable in the current state that it's in. He's missing the sh binary that actually lets you go into the shell. He can't push to the system because he doesn't have the su binary so he cannot remount. There's no way to push files to a PATH location as they are all read only unless you're root. He needs a factory cable or he's screwed.
As for the cable itself, if you Google tbh Motorola factory cable you'll find it. You can also make one from an existing cable, just google around for a guide
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
many thanks =). This cable looks easy, I'll try
Related
I have a Galaxy Nexus that after updating is stuck in a boot loop just recycling the Google logo. There is no ADB access as a result.
Is there anyway I can save my photos? Thanks!
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Like Eddy said. Via fastboot, boot up CWM, either you have it flashed or not.
From CWM, you can access the phone via adb over USB.
In a "adb shell", you can .tar.gz up the stuff you like (or your entire /sdcard). Afterwards you can "adb pull" that off the phone.
Requires quite a bit off commandline, but it's not hard, just cumbersome. If your data is important enough, it's definitely worth it.
EddyOS said:
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Click to expand...
Click to collapse
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
efrant said:
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
Click to expand...
Click to collapse
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
Correct. If your bootloader is locked, you're out of luck. Unlocking wipes everything.
EddyOS said:
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Click to expand...
Click to collapse
Once you boot up CWM, you have adb access to the files on your device. Not sure what "mount" you are talking about, but I have never had to do anything to get files off/on the /sdcard directory other than boot up CWM or my ROM.
Sent from my Galaxy Nexus using Tapatalk
Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
You are not mistaken. In that case, try booting to the stock recovery and use the adb pull command.
Sent from my Galaxy Nexus using Tapatalk
Boot loop
If you are having difficulty with boot loop, pull the battery. I had the same issue with my N1 didn't wipe dalvik cache after an update. And because of the loop couldn't get the timing for fastboot as the bootloop was not giving an indication of when the keypresses would activate the bootloader.
If you are unrooted and stock then try this:
Put device into the bootloader by holding down Vol Up + Vol Down + Power
use your volume buttons to change options next select (with power button) the fastboot option, after use the ADB instructions from the more knowledgeable members (ADB is somewhat cumbersome.... but it works and has saved my bacon) After wards using the Bootloader you should be able to resore to factory settings and reload your info after.
If you are Rooted with a custom bootloader and rom
same as above to get to bootloader, but then wipe your cache, and dalvik cache. Reflash latest ROM and Gapps. You shouldnt lose anything.
Good luck bud.... your Nexus isn't dead.... only in a Coma.... or a political promise...
J
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
danger-rat said:
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
Click to expand...
Click to collapse
Have you tried and gotten that to work in recovery? Although I haven't tried it, I don't think that works in recovery. It is a feature of ICS, so I'm pretty sure you need to be booted into your ROM for it to work.
Sent from my Galaxy Nexus using Tapatalk
sos lge960
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
bibi019 said:
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
Click to expand...
Click to collapse
My guess is this question is more appropriate for the nexus 4 forum
Sent from my Galaxy Nexus
Nooooo, necrobumping is fine, since he has the same issue, and this is the first hit on Google... even though he's on a different device. /s
Sent from my Nexus
Hey, I'm running to a similar problem with this guy.
I stupidly reformated my system files without having a rom on my internal sd.
The question is that I'm reading that I can use the adb to push files in but I'm just new to the whole adb.
How would I get my computer to use the adb?
Sorry for such a noob question -_-;
Edit: So it seems from looking around and reading other forums and faq's that I need to have the phone for the adb to be installed.
Is there away around that so that I can access the adb?
Edit2: Nevermind. Fixed it with a toolkit. Sorry to spam
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2
JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.
RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.
Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars
Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps
If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.
mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.
Then just use the sideload, it works quite well for me.
mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.
No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement
stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone
Hi guys,
I've installed Nexus root toolkit, skip's toolkit, pda net drivers (one at a time, of course) but my device isn't getting recognized in adb and also I'm unable to mount /sdcard using data cable also (tried using multiple cables too). This problem started after I flashed insecure boot image using nexus root toolkit, I think the mount script got messed up somehow. I tried to sideload the cwm but the stock recovery says a message like 'unable to find /sdcard'.
Bootloader unlocked, no custom recovery, no root, jwr66y build . Please suggest me what to do.
Sent from my Galaxy Nexus using xda app-developers app
Does the device boot? Where are you trying to use adb? What are you trying to achieve?
Your best bet, especially if you want help in this forum, is to drop the toolkit and do it manually. It is harder to diagnose problems with what could have gone wrong with a toolkit than if they were to do it without one.
Yeah, the is functioning normally.
I'm trying to flash stock all over again. I tried to sideload cwm using adb.
Sent from my Galaxy Nexus using xda app-developers app
sasuketobi said:
Yeah, the is functioning normally.
I'm trying to flash stock all over again. I tried to sideload cwm using adb.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Use fastboot to get the recovery on your device.
cupfulloflol said:
Use fastboot to get the recovery on your device.
Click to expand...
Click to collapse
So here's more explanation for the problem that I'm facing:
1. Device is not recognized in Fastboot mode, tried with adb from Android SDK too, so i cannot run any of the fastboot commands
2. When i try to flash zips from stock recovery, recovery -> install zip from USB -> screen shows an error at bottom: "unknown partition for path /sdcard"
I the did a restart, gave permission for connection through adb
3. Booted to Recovery -> install zip from adb using adb sideload, then the terminal shows an error: sideload not found (executable, don't remember the error message correctly)
I cant flash a zip due to this. I've also lost my fastboot cable. So if fastboot is my only option does anyone know the commands that need to be typed in terminal commands to accomplish this?
Did you try mounting it in mount, and browsing system from An adb shell or twrp's file browser to see if you can view the contents of /system? If you can tell me what shows up in there.
Sent from my LG-P769 using xda app-developers app
Try adb push after turning it on.
Twrp won't Mount properly with our device
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I tried to mount system under mount but the screen just freezes than unfreeze with system still unmounted. Don't have my kindle with me at the moment so can't check to see if files show up in system. I don't think adb push would help though because I don't think anything can be written to system because it won't mount. Correct me if I'm wrong.
Have you tried from TWRP:
Code:
adb reboot bootloader
Should reboot into fastboot mode without a fastboot cable
narms72 said:
I tried to mount system under mount but the screen just freezes than unfreeze with system still unmounted. Don't have my kindle with me at the moment so can't check to see if files show up in system. I don't think adb push would help though because I don't think anything can be written to system because it won't mount. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nvmd. Just understood what you are saying. Fastboot is your only option
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Does anybody know what happened? Did it become corrupt? I d like to prevent this from happening again.
narms72 said:
Does anybody know what happened? Did it become corrupt? I d like to prevent this from happening again.
Click to expand...
Click to collapse
No idea. This never happened to me. What were the circumstances that occurred before this happened?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
https://www.youtube.com/watch?v=xuM5QAinkUA&feature=youtube_gdata_player heres what happens when you type adb reboot bootloader and what shows up in system and sys.
Failed Post
What other commands is there to get to fastboot? Why is adb missing? I really don't want to buy about her fastboot cable. Thanks.
narms72 said:
What other commands is there to get to fastboot? Why is adb missing? I really don't want to buy about her fastboot cable. Thanks.
Click to expand...
Click to collapse
Sorry I should have been more clear...with the regular USB cable connected.
From terminal on your PC use adb reboot bootloader then your regular USB will act like a Fastboot cable
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
rocketfans14 said:
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
Click to expand...
Click to collapse
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
stunts513 said:
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
Click to expand...
Click to collapse
I have checked the md5sum of the files using a program I found here on xda. I'll try to do the cd from file right now and I'll let you know how that went. Thank you for the quick reply.
Ok, I got it up to the TWRP recovery screen. But how do I continue to flash the stock in step 4 after installing cm10.2 and gapps? Also, I do not have a factory fastboot cable.
EDIT
After installing CM10.2 and gapps, I hit reboot on TWRP and has 'unfortunately, com.android.phone has stop working' message popped up on the screen. Is it because I haven't continue to the section "Flashing back to stock" in step 4?
EDIT2 (I don't think this is related to the bootloader problem but I would like some assistance)
I rebooted again and didn't get the 'unfortunately' messages again. However, when I plug it into my computer, the device doesn't charge when it is active but charges when I put it into sleep mode. Is there any way to fix this issue?
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I see. Where can I find CM11 and how do I flash it? Is it just:
1.put the file into /sdcard
2.reboot into TWRP recovery
3.uh, wipe memory?
4.install CM11
5.reboot
correct me if I'm wrong. I wasn't sure if these are the correct steps because there are a lot of different guides and most of them don't have the same steps.
P.S. Since the kindle only has 8gb, is there a way to free up more memory on the device other than the needed memory space for the os?
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
"Factory reset to go to?" Also, I should put CM11 zip and gapp in sdcard right?
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I'm sorry if this sounds stupid but how do I factory reset my device? I've been working on rooting to installing bootloaders and finally at the point of getting android os on it non stop. Brain cells are dying rapidly...
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
stunts513 said:
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for all the help. Everything went smoothly after your advises.
Update: It was running well for a while until when it ran out of battery and I recharged it, it won't boot into CM anymore. It just boots into TWRP recovery even if I pressed the option to reboot system and normal boot... What should I do?
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I wiped what you said and tried to flash the rom and gapp but when booting, it will still boot into TWRP.
I'll briefly explain what I did prior to the issue.
After everything was all set up, I went to see if there were any updates which there was, the nightlies for CM 11 0518. I hit download and after download was complete, I hit the option "install and reboot". After the orange kindle fire logo came up and briefly after, the blue one, it boot into TWRP. I tried to reboot again but still no changes. So I went ahead and did a factory reset and flashed the two zip files again. The devices still boots into TWRP... I have no idea what to do afterwards and here I am requesting assistance from someone who knows things like these better.
Have you tried wiping internal storage? That's a last resort, maybe somehow your selinux xattribs got messed up. A internal storage wipe would clear them. But it will wipe your sdcard area so backup anything you want to keep over adb first.
Sent from my Amazon Tate using Tapatalk
I haven't tried wiping the internal storage yet. How do I backup over adb? Also,since you said this might be a last resort method, if it fails, is there no other way to fix it? Not even restoring back to its out of the box state and start all over again with rooting and installing bootloaders etc?
PS. I don't know if it is related to what you are talking about at all but when I plug it into my computer, it doesn't recognize my kindle fire.
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
So in short, to backup, I can just use a adb pull command?
After that, I am lost. I don't really understand what you are saying...
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
So the steps are something like:
Backup with adb
Wipe internal storage
Flash the rom and gapp?
Alternative solution:
Restore the whole device
Repeat the root process
Installing the 2nd bootloader again
Flash rom and gapp
And the rest is if I were to restore the device, it is more flexible to use kindle fire first aide than to use TWRP?