After i flashed Kao Droid, my N7 cant boot to system, it just reset to recovery mod. Althoughi tried to wipe data, cache, davilk ...., but it cant boot to system. I read some forums, but all of them say same way " need to boot to bootloader" . I really scared, i just bought my N7 a few days. Please help me (
If you can boot into recovery, i guess that you already have try to flash again the ROM.
Don´t you make a nandroid backup before? Coz you could try to restore it...
Anyways, it seems that all you need to do is flash a bootloader. Maybe you can do it with the toolkit (i don´t know) or if not, just flash the bootloader using fastboot commands, search in the forum and you´ll find the way
Raisone said:
Anyways, it seems that all you need to do is flash a bootloader. Maybe you can do it with the toolkit (i don´t know) or if not, just flash the bootloader using fastboot commands, search in the forum and you´ll find the way
Click to expand...
Click to collapse
You need the bootloader to use fastboot, if he borked it chances are hes gonna have to exchange/RMA
i dont know how to put a rom file on storage of N7 while i cant boot to system. Can you let me know? Please.
P/s: My English is not good, i'm so sorry
Can you get into the bootloader?
i think you are saying you CAN Boot into recovery.. im going to assume cwm..
once in cwm go into i think advance and then mount usb storage. (im using twrp and kinda cant get in my mind where its at in cwm)
Anyway plug usb to the computer and mount as storage. ADB Should work from within recovery. Then use adb from cmd prompt on your (assuming windows computer ) and push a new rom. to the sdcard. unmount the usb storage and flash the rom.. You might have to reboot- recovery..
if you do not know .how to do the above google how to mount usb from recovery and adb push commands..
There is another post with exact instructions.. myself and several others have done this not thinking and wiping out our data/ media then not having a rom to flash ..
wugs tool kit will also fix this for you . but i recommend doing some research and using adb..
if you are afraid of a cmd prompt . look for qtadb.. its a good place for newbie to start .. it looks kinda like a ftp client..
Good Luck .
hold the power button down for 10-15 seconds, and press volume down at tge same time. that should get you into your bootloader.
Thanks everybody for help me. I will try. If i have other problems i will ask later. Thanks again
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
I don't know how to help you, i can only fix a bricked phone if I have TWRP working..........
But here's a tip, once you fix the phone use IOroot for rooting and AutoRec for TWRP, there is no way you can brick it that way
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
If you are able to boot into FASTBOOT you may try to manually flash partitions...
4Freedom said:
If you are able to boot into FASTBOOT you may try to manually flash partitions...
Click to expand...
Click to collapse
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
KillerMOth said:
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
Click to expand...
Click to collapse
Make sure you have installed the last version of d802 driver(search on lg website)
Install "minimal adb and fastboot" search on google or on xda than open windows cmd and type
Code:
cd FOLDER
With folder i mean the path where you have installed adb
Now you can type
Code:
adb devices
If it show something like a number or something that identify your phone
You can type
Code:
adb reboot bootloader
Your phone will be into fastboot mode
Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).
mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...
jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process
here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?
I tried install a root for nougat.
I am stuck on the screen that warns that the device is unlock and the message "your device is booting now ...."
Its vns-21...
I cant off this phone
First:
Wrong forum section.
Second:
Can you access recovery?
If not, flash a suitable recovery in fastboot mode with fastboot, then restore a backup.
Schlengge said:
First:
Wrong forum section.
Second:
Can you access recovery?
If not, flash a suitable recovery in fastboot mode with fastboot, then restore a backup.
Click to expand...
Click to collapse
Yes i have, but i cant wipe "unable to locate /data partition for backup calculations"
styru111 said:
Yes i have, but i cant wipe "unable to locate /data partition for backup calculations"
Click to expand...
Click to collapse
i made a tutorial how to downgrade to MM
good luck
extract boot.img from your firmware and flash it via fastboot
Hey guys I'm in need of some help..I replaced my V20 screen and when I turned my phone on it booted into a yellow screen that's says Rpm crash...Lge crash handler etc etc..Says something about a system dump..I can boot into TWRP..I wipe the device clean..Even installed a new rom..Still won't get past this yellow screen can you guys help.
flymalikcool said:
Hey guys I'm in need of some help..I replaced my V20 screen and when I turned my phone on it booted into a yellow screen that's says Rpm crash...Lge crash handler etc etc..Says something about a system dump..I can boot into TWRP..I wipe the device clean..Even installed a new rom..Still won't get past this yellow screen can you guys help.
Click to expand...
Click to collapse
can you take a photo and post.
push a new boot.img to your phone
depending on model if you have fastboot access you can try to do this
Fastboot erase cache
fastboot erase fota
fastboot erase misc
fastboot erase system
fastboot erase data
then reboot the device back into twrp, re-flash a rom and make sure the kernel is included.
sounds like you flashed a bad boot.img causing the phone not to boot. Or your new screen is causing a issue
Team DevDigitel said:
can you take a photo and post.
push a new boot.img to your phone
depending on model if you have fastboot access you can try to do this
Fastboot erase cache
fastboot erase fota
fastboot erase misc
fastboot erase system
fastboot erase data
then reboot the device back into twrp, re-flash a rom and make sure the kernel is included.
sounds like you flashed a bad boot.img causing the phone not to boot. Or your new screen is causing a issue
Click to expand...
Click to collapse
Here goes a picture
flymalikcool said:
Here goes a picture
Click to expand...
Click to collapse
Yeah its a bad boot.img
Get a boot.img for ur device..
Flash it with twrp or
Fastboot flash boot.img and reboot
Or rerun dirty santa step 3 and reboot.
Team DevDigitel said:
Yeah its a bad boot.img
Get a boot.img for ur device..
Flash it with twrp or
Fastboot flash boot.img and reboot
Or rerun dirty santa step 3 and reboot.
Click to expand...
Click to collapse
Thanks for the help I downloaded the Sprint boot image for my phone flash through TWRP..Same results..TWRP gave me options for partitions I choose boot..
flymalikcool said:
Thanks for the help I downloaded the Sprint boot image for my phone flash through TWRP..Same results..TWRP gave me options for partitions I choose boot..
Click to expand...
Click to collapse
it didn't work went right back to yellow screen
flymalikcool said:
it didn't work went right back to yellow screen
Click to expand...
Click to collapse
Humm.. Try the wipe commands. Then flash my Rom if ur on ls997.
Can you mount all ur stuff with twrp?
Does it show 0byte free space?
Team DevDigitel said:
Humm.. Try the wipe commands. Then flash my Rom if ur on ls997.
Can you mount all ur stuff with twrp?
Does it show 0byte free space?
Click to expand...
Click to collapse
Thanks for the concern and speedy response..Yes I can mount all my stuff..As far as the wipe commands are you speaking about the fastboot commands you posted earlier..
flymalikcool said:
Thanks for the concern and speedy response..Yes I can mount all my stuff..As far as the wipe commands are you speaking about the fastboot commands you posted earlier..
Click to expand...
Click to collapse
Yeah..
Put into fasboot and wipe everything
Fasboot erase
Misc
Fota
Cache
Dalvik
System
Data
Boot
Then boot back into twrp.. Mount everything and flash a stock ls997 rom.
I had this happen before to me. I believe i had to fix partitions on my device using advanced wipe and ext4 wipe options 1 by 1. But it showed free space 0 for everuthing also.
Do you have a backup on twrp that has ur efs?
Yes I have my efs backup
After fastboot commands im having a problem mounting system
flymalikcool said:
After fastboot commands im having a problem mounting system
Click to expand...
Click to collapse
need to wipe the phone using twrp now to mount system again,
if not if it shows 0 bytes the repair system to ext4 and flash a rom..
lastly, if this repair was done with a knock off screen thats your issue, the oem screen and the 3rd party
probably dont spec the same, and the drops in voltage cause the phone to kernel panic and fail, this is a common issue across many phones after
doing a little digging Via google.
flymalikcool said:
After fastboot commands im having a problem mounting system
Click to expand...
Click to collapse
any luck yet?