Related
Hello, so my mom recently came back from China and someone i guess rooted her phone and made it into Chinese, so I attempted to hard reset the phone thinking it would turn it back into a factory setting but that didn't do anything except erase everything which was alright, I also clicked the option for i think it said "partition cache" or something, but that didn't seem to do anything i was following the guide posted here theunlockr(dot)(com)/2012/11/18/how-to-unroot-and-get-the-samsung-galaxy-s-blaze-4g-back-to-stock so then i realized it was because i wasn't in download mode, but I was in fact in recovery mode, and in order for me to be in download mode i followed this guide
"It looks like you're being booted up into the Recovery Mode whereas you're supposed to be in Download mode.
If the key-combination doesn't work and you're unable to boot into Download mode, then try out the following steps and it should do the job. (Windows only, no Mac and Linux!)
(1) Download Fastboot from here
(2) Extract files from the Fastboot archive to your Desktop and you'll get adb.exe along with some other files.
(3) Enable the USB debugging function on your device by simply heading to Menu>>Settings>>Applications>>Development>>USB debugging.
(4) Once enabled, connect your device to your PC via USB cable.
(5) Launch a Command Prompt Window on your Desktop. To do that, simply hold down the Shift button on your keyboard and right-click on any empty area on the screen, then select Open command window here.
(6) In the Command Prompt Window that you just opened, enter the following command:
adb reboot download
(7) And your device will reboot into the Download mode.
That's all.
Hope it helps you to get into download mode and unroot your device.
Thanks! "
but when doing the command prompt window it kept saying
"error device not found" so i individually ran the program fastboot.exe, and adb.exe which i don't think did anything, so i tried to put the phone back into recovery mode, but this time it went into download mode for some reason, and i ran Odin3 v1.85 and it passed and everything but now it just does a reboot loop and when i try to put it in recovery/download mode little green spots slowly appear until i take the battery out because I'm scared of what might happen if the whole screen turns green. Please Help, i looked through most of the threads but i don't see anything close to mine except for the soft brick thread which i can't even do because i can't get into recovery mode. Please and Thank You
wh3elson said:
Hello, so my mom recently came back from China and someone i guess rooted her phone and made it into Chinese, so I attempted to hard reset the phone thinking it would turn it back into a factory setting but that didn't do anything except erase everything which was alright, I also clicked the option for i think it said "partition cache" or something, but that didn't seem to do anything i was following the guide posted here theunlockr(dot)(com)/2012/11/18/how-to-unroot-and-get-the-samsung-galaxy-s-blaze-4g-back-to-stock so then i realized it was because i wasn't in download mode, but I was in fact in recovery mode, and in order for me to be in download mode i followed this guide
"It looks like you're being booted up into the Recovery Mode whereas you're supposed to be in Download mode.
If the key-combination doesn't work and you're unable to boot into Download mode, then try out the following steps and it should do the job. (Windows only, no Mac and Linux!)
(1) Download Fastboot from here
(2) Extract files from the Fastboot archive to your Desktop and you'll get adb.exe along with some other files.
(3) Enable the USB debugging function on your device by simply heading to Menu>>Settings>>Applications>>Development>>USB debugging.
(4) Once enabled, connect your device to your PC via USB cable.
(5) Launch a Command Prompt Window on your Desktop. To do that, simply hold down the Shift button on your keyboard and right-click on any empty area on the screen, then select Open command window here.
(6) In the Command Prompt Window that you just opened, enter the following command:
adb reboot download
(7) And your device will reboot into the Download mode.
That's all.
Hope it helps you to get into download mode and unroot your device.
Thanks! "
but when doing the command prompt window it kept saying
"error device not found" so i individually ran the program fastboot.exe, and adb.exe which i don't think did anything, so i tried to put the phone back into recovery mode, but this time it went into download mode for some reason, and i ran Odin3 v1.85 and it passed and everything but now it just does a reboot loop and when i try to put it in recovery/download mode little green spots slowly appear until i take the battery out because I'm scared of what might happen if the whole screen turns green. Please Help, i looked through most of the threads but i don't see anything close to mine except for the soft brick thread which i can't even do because i can't get into recovery mode. Please and Thank You
Click to expand...
Click to collapse
First, you should post your question in the General section. Second, it seems that you didn't or have not installed device drivers on your PC and that's why there was the "error device not found" message. Third, just flash an English ROM then that might solve the problem with Chinese ROM.
I would redo Odin back to stock from download mode. If your having issues getting into download mode take a look at this helpful post. http://forum.xda-developers.com/showpost.php?p=27360727&postcount=57
Re-stock thread http://forum.xda-developers.com/showthread.php?t=1591601
If it still has the issues, you might have to flash CWM in Odin and wipe everything then run the re-stock again.
To boot to the recovery, hold both volumes and power, release power after it vibrates and continue to hold volumes until recovery boots up, and wipe cache, davlik cache, and wipe data/factory reset. Then reboot and see if it works. If not reboot into recovery again, wipe cache, davlik, system, emmc, factory reset. After that get back into download mode and re-Odin back to stock again.
taodan said:
First, you should post your question in the General section. Second, it seems that you didn't or have not installed device drivers on your PC and that's why there was the "error device not found" message. Third, just flash an English ROM then that might solve the problem with Chinese ROM.
Click to expand...
Click to collapse
Romman0 said:
I would redo Odin back to stock from download mode. If your having issues getting into download mode take a look at this helpful post.
Re-stock thread
If it still has the issues, you might have to flash ]and wipe everything then run the re-stock again.
To boot to the recovery, hold both volumes and power, release power after it vibrates and continue to hold volumes until recovery boots up, and wipe cache, davlik cache, and wipe data/factory reset. Then reboot and see if it works. If not reboot into recovery again, wipe cache, davlik, system, emmc, factory reset. After that get back into download mode and re-Odin back to stock again.
Click to expand...
Click to collapse
Thanks so much guys, the information you guys provided was very helpful especially yours Romman0, i was able to get my phone back into stock condition.
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
I was experiencing issues with my ATT HTC One X with CDM 10.1 on it, so I booted into boot loader and tried to boot up a new ROM, but somehow my initial ROM got deleted, I forgot to back up, and now I have no ROM installed and my phone is stuck in a boot loop. I have been messing with this thing and researching for hours trying all kinds of different things to get it working and nothing has seemed to work.
Can someone please help me?
Did you do a factory reset from the bootloader? If so, you've corrupted the internal memory, and will need to format it before you can move another ROM onto it.
Sent from my Evita
timmaaa said:
Did you do a factory reset from the bootloader? If so, you've corrupted the internal memory, and will need to format it before you can move another ROM onto it.
Sent from my Evita
Click to expand...
Click to collapse
Now that I recall, yes I believe that's exactly what I did.
Where I'm at now, I can't get into recovery. The only thing I can do is get into fastboot. Where do I go from here?
Ok. I'm assuming you have a working adb/fastboot environment on your PC. If you can't get into recovery you may as well try flashing it. Get it from here (I recommend version 2.3.3.1):
http://goo.im/devs/OpenRecovery/evita
Once you've downloaded the file, put it into your working adb/fastboot directory (rename it to something simple like twrp.img). Make sure you're booted into bootloader, connect phone to pc, ensure it says "fastboot usb" on your phone screen, open a command prompt within your adb/fastboot directory then issue the following command:
fastboot flash recovery twrp.img
This will flash the recovery, it only takes a few seconds. When it's finished, issue this command:
fastboot erase cache
Once that's done, select recovery on your phone and it should boot into TWRP recovery. Select mount from TWRP menu, mount usb storage, the storage should now show up on your pc, format it to fat32.
Now you can copy ROM from PC to phone, unmount storage, and you should be able to flash a ROM (make sure you do a full wipe first though).
Sent from my Evita
timmaaa said:
Ok. I'm assuming you have a working adb/fastboot environment on your PC. If you can't get into recovery you may as well try flashing it. Get it from here (I recommend version 2.3.3.1):
Once you've downloaded the file, put it into your working adb/fastboot directory (rename it to something simple like twrp.img). Make sure you're booted into bootloader, connect phone to pc, ensure it says "fastboot usb" on your phone screen, open a command prompt within your adb/fastboot directory then issue the following command:
fastboot flash recovery twrp.img
This will flash the recovery, it only takes a few seconds. When it's finished, issue this command:
fastboot erase cache
Once that's done, select recovery on your phone and it should boot into TWRP recovery. Select mount from TWRP menu, mount usb storage, the storage should now show up on your pc, format it to fat32.
Now you can copy ROM from PC to phone, unmount storage, and you should be able to flash a ROM (make sure you do a full wipe first though).
Sent from my Evita
Click to expand...
Click to collapse
I appreciate the info. I think I understand what to do now. My only problem now is that I think my phone died. The red light blinks for a couple minutes, then it turns on and goes to the HTC quietly brilliant screen. If I hold down the power and vol down buttons it will turn off and then if I hold them down again it will go into the bootloader, but then it will shut off after a few seconds. Is it because it's dead and how do I get it charge?
Stop trying to turn it on. If you do that too many times while it has very low charge you can kill the battery to the point where it's not usable at all anymore.
Leave it turned off, plug it into a wall charger overnight and then try again.
Sent from my Evita
timmaaa said:
Stop trying to turn it on. If you do that too many times while it has very low charge you can kill the battery to the point where it's not usable at all anymore.
Leave it turned off, plug it into a wall charger overnight and then try again.
Sent from my Evita
Click to expand...
Click to collapse
I got it back into recovery after running the commands you told me. I then moved my ViperXL 3.2.7 ROM file over to the phone. The install started and then froze one the ViperXL screen and never went any farther. I am back in recovery again, but I don't know what to do again because that ROM failed.
So now I got the ViperXL installer to go all the way through the install and it said it was successful, but now it is doing the boot loop again. It reboots, goes to the HTC screen, turns off, and just keeps repeating itself.
lcderrick said:
So now I got the ViperXL installer to go all the way through the install and it said it was successful, but now it is doing the boot loop again. It reboots, goes to the HTC screen, turns off, and just keeps repeating itself.
Click to expand...
Click to collapse
What hboot? S-on or off??
Sent from my HTC One XL using xda premium
You probably need to flash the boot.img manually.
Sent from my Evita
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?
boot-to-root is for Android O, you have to follow this guide
I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.
falsh factory image inside the bootloader, don't need to go to recovery.
Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.