Related
I was copying my SD Card to my computer. At some point I forgot I was transferring files and disconnected the usb cable. I reconnected the cable and all seemed right. So I continued on and rebooted my phone.
After a few minutes I noticed the green notification light blinking and assumed I had a text or mail. When I hit the power button on top to wake the phone the screen never came on. I pulled the battery and tried to reboot the phone. It would just vibrate 5 times and the screen would stay blank. So i tried recovery and it would work only with the USB cord plugged in. But it wouldn't do a nandroid backup or even see the sdcard.
when in recovery I get the error E:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
I tried getting a adb shell but it says no device connected
I tried using fastboot flash boot boot.img and fastboot flash system system.img
they would error with FAILED (remote: signature verify fail)
anyone have any suggestions?
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
fader01 said:
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
Click to expand...
Click to collapse
Sounds like you corrupted a partition or two. Just get an RUU PB31IMG.zip, copy it your card (you may have to take it out and fix it in windows first), and let bootloader see it. There are ways to manually NANDroid your phone in ADB/Recovery, but it doesn't sound like you want to go that deep nor do I know how to tell you to do it from the command line.
Good luck!
Thanks for the reply. The phone will not mount or see the SD Card. I put the sd card in my storm and it formatted it I put it into the Incredible but it still will not mount the SD Card.
I did go to the verizon store and my hopes where they had some way to format the partitions and force the OS on it. The guy looked at the phone and said we dont have a recovery console for the Incredible so I will have a new one sent to you probably will be Tuesday.
I thought the Dallas Cowboys boot screen and fastboot screen would tell him something wasnt right but he didnt know or he didnt care. I also thought it was odd he gave me the phone back. Shouldnt he have kept it to send back in?
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
illalliance said:
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
Click to expand...
Click to collapse
I got the 5 vibration deal when I was trying to boot into recovery.....but was pressing volume up/power, instead of vol down/power......the 5 vibrations are a Qualcomm diagnostic test.
SLOflatlander said:
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
Click to expand...
Click to collapse
I had googled that before making this post, nothing I found had helped me. I cannot say, for sure, that I found the post you are referring to though. I did finally manage to get the system to see the sdcard and PB31IMG.zip. I took the rom.zip from the Froyo RUU and I renamed it pb31img.zip. It went through and flashed everything but still nothing. When I later tried to do the same thing with the rom.zip from the 2.1 RUU the system said that it was an older version and would not flash it. So this seems to me that the flash went OK. Its like the main OS partition isn't bootable or something the system knows the OS is there it just cannot boot to it.
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
I trashed my internal partitions yesterday and used this method to fix it.....had to end up un-rooting and starting over after I got the partitions back in order....but it did fix the problem.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
Thanks a lot. I will work on it after work tonight.
I need help understanding why I'm stuck in reboot loop with my EVO 4G.
I originally was trying to root the device using unrevoked3 but getting the ERROR "Backup CID is Missing" message and unable to proceed. I followed the instructions at http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html which talk about troubleshooting this. It talks about going into recovery mode to see if I've lost the recovery mode which I did (black screen with phone and read arrows). It says to reboot but I was unable to so I unplugged the battery.
Since then I have been stuck in a mode where the device boots but the sdcard is not recognized and upon completion of boot up it shuts down and vibrates five times. I did a bunch of research last night on understanding what I thought I needed to do alleviate this. My thought was since I was stuck without a recovery image I need to flash new one. At this point I'm fine with not being rooted with all the trouble I've had.
I downloaded the latest stock recovery rom (3.70.651.1) from http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html and pushed it to my sdcard under the name PC36IMG.zip (with two files .info and recovery.img). I restarted my phone via HBOOT and it sees the zip file, reads it in, goes to checking and then does nothing (back to HBOOT screen). I don't get what I'm doing wrong. I also tried getting the stock image from http://forum.xda-developers.com/showthread.php?t=874091 but I can't seem to open the firmware.zip file to try that recovery image.
Again I just want to get back to stock ROM and recovery files now. Any help would be greatly appreciated!
So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
GH0 said:
try reflashing the stock pulled .tar file? and a nandroid backup/stock OS?
Looks like some files may be corrupt.
Click to expand...
Click to collapse
I have tried reflashing the stock pulled .tar file and resetting to factory defaults, neither of these worked. Are the files 'gaudi_bootimage.jpg' and 'charging.jpg' something I can place in a specific directory that will avoid this boot up into recovery problem? I'd like to overwrite those potential corrupt files with good ones.
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
I saw you wiped fator reset. But dis you also wipe the cache and dalvik? Then do clean install with CWM 5.x.x.x ? I would recomend that id u haven't tried thus yet
eph5networks said:
So I rooted with Odin using the "SPH-D710_Zedomax_Kernel.tar" and then unrooted with Odin using the "acs-eg30-stock-kernel-pulled.tar". Once I unrooted everytime I boot my phone up I get this error message:
'gaudi_bootimage.jpg' draw failed
and I boot into System Recovery (manual mode), and if my phone is plugged into laptop or wall charger when I power down I receive the following error message
'charging.jpg' draw failed
Even when I root back, it still always boots into recovery mode and boot up error message is replaced with the Galaxy S2 GT-I9100 splash screen, but I still get the 'charging.jpg' draw failed error.
On both occasions (root or unroot) I can still select reboot system now and the phone finally boots up fine, but I'm trying to eliminate the jpg boot and charge error messages and boot directly into he phone without having to select it in recovery. I have done a complete factory wipe with the same results as described above. Any suggestions?
Click to expand...
Click to collapse
Hello, I got the same problem as you. I still don't know how to do it. please, Let me know if you know any way to fix it. Thanks
KCRic said:
They are in /mnt/.lfs
I'll see if I can pull them and post for you.
Oh wow!
There's a treasure trove of stuff in this directory. I think it's hidden but using Android Webkey I got to it. I'll post some other "boot" images from here. The initial "Samsung Galaxy S II" image isn't the only one. I like the Iron Droid one, though it doesn't seem complete.
Anyway, here's the .zip of all the images in that directory.
Click to expand...
Click to collapse
Alright a quick update (not positive):
I copied the files onto the /mnt folder, but unfortunately after I copy them they still don't appear in the directory. I reboot and I still receive the same 'gaudi_bootimage.jpg' draw failed & 'charging.jpg' draw failed. I do have root access by the way and I'm copying these to the directory using Root Explorer.
I also took the following steps:
Installed CWM 5.0.2.3
Performed a nanroid backup
formatted the system volume under 'mount and storage'
wiped data/factory reset
wiped cache partition
wiped dalvik cache
All that still with no success.
Another thing I'm noticing is when these error messages show (on boot & after power down while connected to charging source) it automatically boots into recovery. There has to be some way or place these files are being called for me to replace them to make this annoying issue go away. Any more suggestions?
So you have tried reinstalling CWM to see if it helps?
Seems (no expert here) that something is corrupted. Not sure exactly what but possibly part of the internal storage or the primary or secondary bootloader. I really hate to jump to something that extreme but i just don't see another reason it would be acting up like that.
I would download CWM one more time and check the MD5 before using ODIN to flash it. If it still does it - return to stock (remove the yellow triangle if you have it) and take it back to the store. Should be under warranty still.
Did you ever solve this problem as i have the same issue.
sscoleman said:
Did you ever solve this problem as i have the same issue.
Click to expand...
Click to collapse
Unfortunately none of these options resolved it. Still pending.
got d boot image running....
Hey i 1st got a stock samsung boot .zip file and den used sgs2 boot changer to apply d img it worked....!!!! Thank got for dat .... Still dont knw wat to do abt d charging. Jpg though... D app works for dis model too... Try it out....
Hi there, I recently bought an used unlocked LG G PRO E988 (made in korea) version. I rooted it. I tried to flash a custom rom but got stuck in boot loop with a security warning saying "SECURE booting ERROR!! Cause: boot certification verify" But while booting if I kept the volume up and power botton pressed it would give me "SECURE booting ERROR!! Device is unlocked so booting success" , However i could not get into the download mode no matter which ever key combination i tried. Finally pressing the volume up ,home key and power botton at the same time while putting back the battery on i ran into recovery mode and flashed a new rom "sphinx" and it was working fine, though I kept getting the "SECURE booting ERROR!! Device is unlocked so booting success" while booting up. I installed the Philz touch recovery while installing sphinx rom but day before yesterday I wanted to install the default cwm recovery and flash sphinx again with less apps,so from the recovery mode i wiped dev cache,wiped cache partion (and i think i wiped data/factory reset as well ) installed the sphinx rom again and rebooted from sphinx installation screen where i need to check a sqaure box to reboot. but my phone got stuck in boot loop again and with the same security warning "SECURE booting ERROR!! Cause: boot certification verify" but this time pressing the volume up and power button while connecting usb or putting back the battery didn't change the security warning to "SECURE booting ERROR!! Device is unlocked so booting success" neither could i get into my recovery mode. And i have always failed to log into download mode. I read almost all the threads about how to get into g pro download mode but never succeed. The only screen i was getting besides "hard reset" and "boot logo with security warning" was a screen with this message "Recovery mode,Using this mode, service center can back up and recover your data. Press and hold the POWER key more than 8 seconds to reboot and continue using phone." which would eventually take me to the boot loop again if i kept pressing the power button. sigh ! And at this point my phone was not being detected by my pc. I tried "[GUIDE] Optimus G Pro Full Hard Brick fix" by ricanares, but i couldnt get to download mode so the process failed for me After searching for hours and reading tutorials i found out about pdanet drivers and mtk droid tools. which finally detected my phone in pc only when the creen " Recovery mode,Using this mode, service center can back up and recover your data. Press and hold the POWER key more than 8 seconds to reboot and continue using phone." appears. Using mtk droid tools i tried to use a boot image (from an extracted .tot file)and recovery(from same .tot file) but i was getting an error saying no split boot image found.Tried using extracting a .tot file and sideloading the recovery.bin and boot.bin .Tried pushin and sideloading cusom recovery.apk files and all efforts in vein. For any files i send using sideload my phone shows an error "E:footer is wrong ; E: signature verification failed" Using mtk droid tools i could enter into a recovery mode but i dont think it is the cwm recovery mode. it has fewer options. I am so lost at this point ! I need some expert help ...
Things working
1. Boots into stock recovery using mtk tools.
2. Pc recognizes device as LG Android net phone
3.Mtk tools recognizes the device as LG E988
4.Can use adb sideload options to send files to phone in recovery mode (but phone outputs error as 1st attached image )
5.In recovery mode I can see and go into /cache folder using update from cache option.but theres nothing there
THINGS NOT WORKING
1.Doesnt Boot into recovery mode using physical buttons
2.Doesnt Boot into download mode
3.Cant get into fastboot mode with adb commands
4.Doesnt mount sd card .(tried formatting sd card with sdformatter)
5.Don't have a proper backup of my phone.
6.Can't extract downloaded .kdz files to get the boot.img and recovery.img files (tried using lg p970 rom converter, optimus L9 image extractor and lg extract)
HELP
1) Does anyone have extracted .kdz for e988 that has split boot image ?
2)How can i fix E:failed to mount /sdcard error.
3)How do i get to download mode in e988 ? is it possible that i deleted the mode ?
sd091989 said:
Hi there, I recently bought an used unlocked LG G PRO E988 (made in korea) version. I rooted it. I tried to flash a custom rom but got stuck in boot loop with a security warning saying "SECURE booting ERROR!! Cause: boot certification verify" But while booting if I kept the volume up and power botton pressed it would give me "SECURE booting ERROR!! Device is unlocked so booting success" , However i could not get into the download mode no matter which ever key combination i tried. Finally pressing the volume up ,home key and power botton at the same time while putting back the battery on i ran into recovery mode and flashed a new rom "sphinx" and it was working fine, though I kept getting the "SECURE booting ERROR!! Device is unlocked so booting success" while booting up. I installed the Philz touch recovery while installing sphinx rom but day before yesterday I wanted to install the default cwm recovery and flash sphinx again with less apps,so from the recovery mode i wiped dev cache,wiped cache partion (and i think i wiped data/factory reset as well ) installed the sphinx rom again and rebooted from sphinx installation screen where i need to check a sqaure box to reboot. but my phone got stuck in boot loop again and with the same security warning "SECURE booting ERROR!! Cause: boot certification verify" but this time pressing the volume up and power button while connecting usb or putting back the battery didn't change the security warning to "SECURE booting ERROR!! Device is unlocked so booting success" neither could i get into my recovery mode. And i have always failed to log into download mode. I read almost all the threads about how to get into g pro download mode but never succeed. The only screen i was getting besides "hard reset" and "boot logo with security warning" was a screen with this message "Recovery mode,Using this mode, service center can back up and recover your data. Press and hold the POWER key more than 8 seconds to reboot and continue using phone." which would eventually take me to the boot loop again if i kept pressing the power button. sigh ! And at this point my phone was not being detected by my pc. I tried "[GUIDE] Optimus G Pro Full Hard Brick fix" by ricanares, but i couldnt get to download mode so the process failed for me After searching for hours and reading tutorials i found out about pdanet drivers and mtk droid tools. which finally detected my phone in pc only when the creen " Recovery mode,Using this mode, service center can back up and recover your data. Press and hold the POWER key more than 8 seconds to reboot and continue using phone." appears. Using mtk droid tools i tried to use a boot image (from an extracted .tot file)and recovery(from same .tot file) but i was getting an error saying no split boot image found.Tried using extracting a .tot file and sideloading the recovery.bin and boot.bin .Tried pushin and sideloading cusom recovery.apk files and all efforts in vein. For any files i send using sideload my phone shows an error "E:footer is wrong ; E: signature verification failed" Using mtk droid tools i could enter into a recovery mode but i dont think it is the cwm recovery mode. it has fewer options. I am so lost at this point ! I need some expert help ...
1) Does anyone have an original .kdz file for e988 (i believe its E98820b_00.kdz) or extracted .kdz that has split boot image ?
2)How can i fix E:failed to mount /sdcard error.
3)How do i get to download mode in e988 ? is it possible that i deleted the mode ?
Click to expand...
Click to collapse
"However i could not get into the download mode no matter which ever key combination i tried."
Have you tried:
1) remove battery
2) hold down both volume buttons and power button
3) insert power cord while keeping buttons held down
4) download mode is yours to cherish??
And for once you get into download mode: your KDZ! (or more here)
From there to go here and do more things. Things cannot be left undone. They hate that.
" SECURE booting ERROR!! Device is unlocked so booting success"
This is normal once you install a custom recovery. As long as your phone works, ignore.
culot said:
"However i could not get into the download mode no matter which ever key combination i tried."
Have you tried:
1) remove battery
2) hold down both volume buttons and power button
3) insert power cord while keeping buttons held down
4) download mode is yours to cherish??
And for once you get into download mode: your KDZ! (or more here)
From there to go here and do more things. Things cannot be left undone. They hate that.
" SECURE booting ERROR!! Device is unlocked so booting success"
This is normal once you install a custom recovery. As long as your phone works, ignore.
Click to expand...
Click to collapse
Thanks for your response. Yes i tried that but didn't work. I tried with and without battery both. actually tried numerous times.Only the soft keys keep flashing and nothing else happen. But i will give it a shot again. Plus the secure booting error has changed to "SECURE booting ERROR!! Cause: boot certification verify"-- is it just because I am back to stock recovery ? If only i could get into download mode life would have been a lot easier !! (finger crossed)
sd091989 said:
Thanks for your response. Yes i tried that but didn't work. I tried with and without battery both. actually tried numerous times.Only the soft keys keep flashing and nothing else happen. But i will give it a shot again. Plus the secure booting error has changed to "SECURE booting ERROR!! Cause: boot certification verify"-- is it just because I am back to stock recovery ? If only i could get into download mode life would have been a lot easier !! (finger crossed)
Click to expand...
Click to collapse
Still boned? The LG Support Tool worked for me once, when I was in a similar situation way back last month when I first began smartphoning.
I was in this *exact* same situation after trying to flash my first ROMs and recovery stuff, but I don't remember how I got out of it. :| ACk!
Yupp still stuck . Will try again later tonigh. Didn't get a chance to sit with it the whole day. Hoping for the best !!
sd091989 said:
Yupp still stuck . Will try again later tonigh. Didn't get a chance to sit with it the whole day. Hoping for the best !!
Click to expand...
Click to collapse
Oh! One thing to remember: always plug your USB cable directly into your computers motherboard USB ports, and avoid plugging into USB hub ports (like via a monitor or keyboard). If a desktop: that also means don't use the ports on your computer system. always use the rear ports that plug directly into your motherboard.
(A couple of times I was able to flash a stock TOT/KDZ via the USB hub on my monitor, but that is not a feat that is repeatable for me.)
This makes *all* the difference for me.
culot said:
Oh! One thing to remember: always plug your USB cable directly into your computers motherboard USB ports, and avoid plugging into USB hub ports (like via a monitor or keyboard). If a desktop: that also means don't use the ports on your computer system. always use the rear ports that plug directly into your motherboard.
(A couple of times I was able to flash a stock TOT/KDZ via the USB hub on my monitor, but that is not a feat that is repeatable for me.)
This makes *all* the difference for me.
Click to expand...
Click to collapse
Hey ,thanks for the tip. I am using the mobo usb ports. So today i was able to flash pacman rom (its the only one that i can flash in adb sideload actually... couldnt flash the stock rom for signaature error and footer is wrong error) But now getting this new error "assert failed run_program("/system/bin/loki.sh") ==0 )"
E: Error in /tmp/update.zip
(status 7)
p.s- my android version got updated to 4.4.4 in the process !
I feel i am getting close to retrieve my phone back to normal ; yet so far. :S
sd091989 said:
Hey ,thanks for the tip. I am using the mobo usb ports. So today i was able to flash pacman rom (its the only one that i can flash in adb sideload actually... couldnt flash the stock rom for signaature error and footer is wrong error) But now getting this new error "assert failed run_program("/system/bin/loki.sh") ==0 )"
E: Error in /tmp/update.zip
(status 7)
p.s- my android version got updated to 4.4.4 in the process !
I feel i am getting close to retrieve my phone back to normal ; yet so far. :S
Click to expand...
Click to collapse
my phone can get into download mode but stuck at boot loop, i cant use lg tool to recover cuz it says my battery is empty but it is fully charged :/
kdz tool aint working cuz it keeps aborting :/
bagslayer said:
my phone can get into download mode but stuck at boot loop, i cant use lg tool to recover cuz it says my battery is empty but it is fully charged :/
kdz tool aint working cuz it keeps aborting :/
Click to expand...
Click to collapse
How do you get into download mode ?
sd091989 said:
Hey ,thanks for the tip. I am using the mobo usb ports. So today i was able to flash pacman rom (its the only one that i can flash in adb sideload actually... couldnt flash the stock rom for signaature error and footer is wrong error) But now getting this new error "assert failed run_program("/system/bin/loki.sh") ==0 )"
E: Error in /tmp/update.zip
(status 7)
p.s- my android version got updated to 4.4.4 in the process !
I feel i am getting close to retrieve my phone back to normal ; yet so far. :S
Click to expand...
Click to collapse
The Why: You can't flash that via the stock recovery. You need to use FreeGee to flash CWM or TWRP.
You can get your system into stock recovery: this is good! Does ADB recognize? If not check Windows drivers. If ADB recognizes it, and you can 'adb shell' into it, maybe I could walk you into rooting and installing a custom recovery via the shell?
1) If not already, have ADB at hand. It is your best friend.
---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------
bagslayer said:
my phone can get into download mode but stuck at boot loop, i cant use lg tool to recover cuz it says my battery is empty but it is fully charged :/
kdz tool aint working cuz it keeps aborting :/
Click to expand...
Click to collapse
LGFlashtool.exe says battery is empty?
culot said:
The Why: You can't flash that via the stock recovery. You need to use FreeGee to flash CWM or TWRP.
You can get your system into stock recovery: this is good! Does ADB recognize? If not check Windows drivers. If ADB recognizes it, and you can 'adb shell' into it, maybe I could walk you into rooting and installing a custom recovery via the shell?
1) If not already, have ADB at hand. It is your best friend.
---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------
LGFlashtool.exe says battery is empty?
Click to expand...
Click to collapse
LG Mobile Support tool says battery is empty
bagslayer said:
LG Mobile Support tool says battery is empty
Click to expand...
Click to collapse
Dude, you are so in the wrong program:
LG Flash Tool 1.8 -- this is what handles your TOTs.
Err, wait, you're on E988? Nevermind, no TOTs for you. I've only flashed KDZ a few times, and I don't recall off hand. :| I think it was this one that worked for me: here.
culot said:
The Why: You can't flash that via the stock recovery. You need to use FreeGee to flash CWM or TWRP.
You can get your system into stock recovery: this is good! Does ADB recognize? If not check Windows drivers. If ADB recognizes it, and you can 'adb shell' into it, maybe I could walk you into rooting and installing a custom recovery via the shell?
Yes I can actually get into shell using adb. and my device is recognized as an adb device in device manager. If u can walk me into rooting through adb that would be awesome. specially if i could install a cusom recovery. I spent a bit of time yesterday looking into the files in my phone through adb. tried to change the default.prop file , and push in a custom recovery, but no luck. and i could be wrong but I think for some reason my internal storage (/sdcard) is not being mounted.and same for my external sd card.
But i highly appreciate your response dear Thanks alot for looking into it.
Click to expand...
Click to collapse
culot said:
Dude, you are so in the wrong program:
LG Flash Tool 1.8 -- this is what handles your TOTs.
Err, wait, you're on E988? Nevermind, no TOTs for you. I've only flashed KDZ a few times, and I don't recall off hand. :| I think it was this one that worked for me: here.
Click to expand...
Click to collapse
Yes I can actually get into shell using adb. and my device is recognized as an adb device in device manager. If u can walk me into rooting through adb that would be awesome. specially if i could install a cusom recovery. I spent a bit of time yesterday looking into the files in my phone through adb. tried to change the default.prop file , and push in a custom recovery, but no luck. and i could be wrong but I think for some reason my internal storage (/sdcard) is not being mounted.and same for my external sd card.
But i highly appreciate your response dear Thanks alot for looking into it.
SO after trying to install the root.zip I tried running nifty.bat . And this is the error i get.
culot said:
The Why: You can't flash that via the stock recovery. You need to use FreeGee to flash CWM or TWRP.
You can get your system into stock recovery: this is good! Does ADB recognize? If not check Windows drivers. If ADB recognizes it, and you can 'adb shell' into it, maybe I could walk you into rooting and installing a custom recovery via the shell?
1) If not already, have ADB at hand. It is your best friend.
---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------
LGFlashtool.exe says battery is empty?
Click to expand...
Click to collapse
culot said:
Dude, you are so in the wrong program:
LG Flash Tool 1.8 -- this is what handles your TOTs.
Err, wait, you're on E988? Nevermind, no TOTs for you. I've only flashed KDZ a few times, and I don't recall off hand. :| I think it was this one that worked for me: here.
Click to expand...
Click to collapse
sd091989 said:
SO after trying to install the root.zip I tried running nifty.bat . And this is the error i get.
Click to expand...
Click to collapse
wow that is such a mean one :C "It doesnt work so we never met okay?" srsly who would do that >.>
bagslayer said:
wow that is such a mean one :C "It doesnt work so we never met okay?" srsly who would do that >.>
Click to expand...
Click to collapse
No doubt, what kind of jerkoff would do that!
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Leonniar said:
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Click to expand...
Click to collapse
Can you flash full rom with mi flash tool
Rares6567 said:
Can you flash full rom with mi flash tool
Click to expand...
Click to collapse
Already did, it didn't work...
Leonniar said:
Already did, it didn't work...
Click to expand...
Click to collapse
Maybe is some motherboard issues?
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Leonniar said:
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Click to expand...
Click to collapse
There is no volume buttons problem?
If no maybe you should reflash whole phone, fastboot, recovery, all, using edl ig.... I don't have this phone or any Snapdragon phone, so I don't really know....
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Leonniar said:
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Click to expand...
Click to collapse
So then why your phone goes to fastboot?
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Leonniar said:
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Click to expand...
Click to collapse
It seems that this a software bug ig, can you try go to recovery and flash the rom?
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Leonniar said:
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Click to expand...
Click to collapse
So where u downloaded the fastboot rom, there is a recovery rom too :
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Be sure u download the recovery rom not fastboot.
Btw use your miui version u had
Tho I'm not 100% sure if you flashed the fastboot rom correctly, did u :
1. Open MiFlashTool : download the tool from here if you don't have it ---> https://xiaomiflashtool.com/
2. Select your rom ( make sure your path to the rom isn't long and the folder/folders don't have long names )
3. Connect your phone
4. Click Refresh ( to make your device appear)
5. And click flash
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Leonniar said:
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Click to expand...
Click to collapse
Ok so to fix the error : go to miflashtool folder and create a new folder called : log
Fixed the start up error, I get the screen that says "Please install driver", I press Install and I get this:
https://prnt.sc/I53g6bs_8i5w
Pressing ok gets me back to the "Please install driver" screen
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Rares6567 said:
It seems that this a software bug ig, can you try go to recovery and flash the rom?
Click to expand...
Click to collapse
flashing miui_APOLLOEEAGlobal_V12.5.4.0.RJDEUXM_451a2324af_11.0.zip from stock recovery is good idea, you can do this from MicroSD card to circumvent any usb issues you are obviously facing on fastboot.
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
So it worked?
This "error" isn't an "error" so don't worry about it
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
This error is normal since you are not re-locking the bootloader.
If some functions are inoperative.
Try to flash the same rom (fastboot) that you had when you bought the phone, probably an A11.
Use clean all(flash_all.bat).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/