Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Cosmin Petrisor said:
Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
View attachment 2999210
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Related
Hey i just installed the new build of CM9 01262012.
I installed it and then i wanted to install the google apps with rom manager.
After that the phone started and i needed to click on the android logo for the setup wizard, after i pressed that the setup wizard crashed each time.
Now i am stuck at the boot if i wanna boot my phone i won't get further then the Samsung Galaxy SII GT-I9100 screen with the yellow triangle.
When i got into the boot mode (power + volume down) it says downloading... do not turn off the phone. i waited untill it finishes but it is stuck on this screen also.
I can't boot at all and also not on the boot mode.
What can i do to fix this plz help me i'm quite a noob with android
I tried volume up + power now i am doing a new recovery from a zip file. hopefully this works it says install from sdcard complete.
yes it worked out i got CM9 running again now check if i can install the google apps manualy
xeoMe said:
Hey i just installed the new build of CM9 01262012.
I installed it and then i wanted to install the google apps with rom manager.
After that the phone started and i needed to click on the android logo for the setup wizard, after i pressed that the setup wizard crashed each time.
Now i am stuck at the boot if i wanna boot my phone i won't get further then the Samsung Galaxy SII GT-I9100 screen with the yellow triangle.
BOOT LOOP
http://forum.xda-developers.com/showthread.php?t=1108499
When i got into the boot mode (power + volume down) it says downloading... do not turn off the phone. i waited untill it finishes but it is stuck on this screen also.
I can't boot at all and also not on the boot mode.
You tried actually understanding the basics before flashing ???
Downloading mode is part of flashing stock roms have you connected ODIN ???
jje
Click to expand...
Click to collapse
I have no boot loop anymore, i know it's not the right topic or section but i have cyanogemod 9 running now but i don't have the google apps or any folder app where i can browse to my sd card to install the google apps, how can i fix this??
the apps i have and what are probally usefull are (Dev Tools, ROM Manager, Superuser)
i can't browse to my sd so cannot install market or other things (
xeoMe said:
I have no boot loop anymore, i know it's not the right topic or section but i have cyanogemod 9 running now but i don't have the google apps or any folder app where i can browse to my sd card to install the google apps, how can i fix this??
the apps i have and what are probally usefull are (Dev Tools, ROM Manager, Superuser)
i can't browse to my sd so cannot install market or other things (
Click to expand...
Click to collapse
Probably not the right topic, but my answer isn't based on fact and/or experience with CM9 - for good reasons, I don't do betas, ever - so we're quits...
Haven't read your post history, but you seem to be yet another new guy who is flashing an unstable beta ROM without previous experience and/or knowledge.
I can't for the life of me understand why inexperienced people do this. Presume there's some overriding urge to have The NextBigThingCoolLolzz on the phone...
DON'T!!!.
Read every sticky here, read every FAQ. If you think you understand - you don't. Read, read and read again.
Think you've got it it? You haven't. Read some more.
Then - and only then - try and flash a 2.3.6, never an ICS. If that goes well, read and read and read.
Then you're ready to take the consequences of flashing beta buggy ROMs (and that's what they are - could use stronger terminology, but I respect the devs..), and you can't say you haven't done your research etc.
Nothing personal. You're just diving into the deep end with lead-filled boots. Never going to end well, yes?
xeoMe said:
i have cyanogemod 9 running now but i don't have the google apps or any folder app where i can browse to my sd card to install the google apps, how can i fix this??
Click to expand...
Click to collapse
I'm honestly lost for words.
I really want to post insults and images, but none of them would be good enough . Just ... wow.
xeoMe said:
I have no boot loop anymore, i know it's not the right topic or section but i have cyanogemod 9 running now but i don't have the google apps or any folder app where i can browse to my sd card to install the google apps, how can i fix this??
the apps i have and what are probally usefull are (Dev Tools, ROM Manager, Superuser)
i can't browse to my sd so cannot install market or other things (
Click to expand...
Click to collapse
Flash back to stock. You clearly have no business flashing such an immature ROM, because you are apparently not equipped to deal with any issues that arise from using it.
Only used this once, but I now feel the need to bookmark it...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
B3311 said:
Sensitive soul, aren't you...
Do your best. I don't get too worried by keyboard hardmen.
Click to expand...
Click to collapse
It was aimed at the OP, not your reply!
oinkylicious said:
It was aimed at the OP, not your reply!
Click to expand...
Click to collapse
Got that, my quick edit wasn't quick enough Sorry.
I got the same issue
Ixdankd said:
I got the same issue
Click to expand...
Click to collapse
You should probably flash back to stock too, then.
Sent from my GT-I9100 using XDA App
Hello,
My LG-D280N is bricked... i think... every time it boots it goes on a purple screen called Demigod crash handler, it also does the same thing when i try to factory reset it
So i had no choice but to flash a new room to hopefully fix it, THANKFULLY it does go to download mode without crashes and it does show up on my device manager as "Android bootloader interface" but even so the flashtool says port(USB or Serial) not found, here is what the phone says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i was writing all that, it actually booted to android!!!! but there are infinite " app stopped" messages, it's impossible to go to settings and try to hard reset or rather it's impossible to go anywhere, looks to me like re-flashing a brand new stock rom is the only choice
i should say that i put this phone in my closet two months ago and it was fine! when i tried to use it today it was like that but anyway, is there anything i can do? I really need to fix that phone
Thanks alot, i really appreciate any help
An update... the phone responds to fastboot commands from ADB tools, it doesn't show up on "adb devices" list though
Wonder if there is a way to use to use fastboot commands to flash a kdz file?
More updates... i used a tool to extract everything from the KDZ file and reflashed the following files like this:
fastboot flash boot boot.bin
fastboot flash factory factory_475136.bin
fastboot flash factory recovery.bin
fastboot flash aboot aboot_144384.bin
fastboot flash aboot abootb_150528.bin
Now i could of have done something either right or extremely stupid BUT ever since i did that factory reset mode actually worked! no more demigod crash handlers and i also stopped seeing those small "boot verification errors" in the corner and the phone actually booted and saw the initial welcome screen, so it actually factory reseted! BUT even though it did I STILL saw the sea of "*instert app here* has stopped" which makes it impossible to navigate the phone
But for whatever reason, it's now stuck on the startup logo after a reset, well even if i screwed up badly, download mode still works like before sooo it's not much different, at the very least i got rid of the stupid demigod crash handler
I've been working on that phone for hours now... been researching on google with little to no information about this at all, most solutions involve the flash tool WHICH doesn't work so i had to come up with my own ideas... and to make matters worse nobody here has gave me clues on how to fix it which is why i give these updates, maybe all this information will help you come up with a solution
Another update... i was wondering why it wouldn't be detected by my flashtool... until it hit me... the download mode itself has problems, thankfully fastboot still worked and i was able to reflash it using one of the files i extracted from the KDZ file
After this, my download mode now works correctly, it displays everything right and is now recognized by the flashtool! finally some real freaking progress, working on this thing is such a pain but finally im getting somewhere, but it's not over yet, right now im waiting for the device to reach 40% of charge before i flash the rom, hopefully no errors will occur as it has already been a HUGE pain and time consuming
Final update... i have successfully flashed the stock rom, after a whole day of trial and error i did it, let me summarize
My problem was mostly that the download mode itself needed to be reflashed, for whatever reason it was broken or not properly configured but whatever the case, it needed to be reflashed using fastboot in order to work correctly and be recognized by the LG Flashtool, after i reflashed it, it was fine and the LG Flashtool FINALLY recognized my device, but the LG Flashtool would CRASH whenever i clicked the "Read Phone Information" button, not sure why but i tried 4 times until it finally worked, not sure what happened there but who cares, it worked out, then it finally started flashing until it said "error connecting to the server", took me sometime and research to realize that it's SUPPOSED to do that and that i should ignore the message and NOT close it because if i do the whole flashtool stops, after this i let it sit in the background and do all the flashing, it was fine until 77%, it gave me an error message and said that i should try to reset my device back into download mode, then it retried doing the whole process all over again AND THANKFULLY this time it successfully did it, the phone now boots to Android as normal, the sea of "app stopped" message is also gone thankfully and so that's pretty much it...
My absolute stupid mistakes and problems with this could help other people avoid those same mistakes and problems so i won't delete the post since as i said, it can prove to be useful to others
Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
Hello friends, I hope you are well. I am writing to everyone to see if anyone can help me with this big problem.
Yesterday install the Rom Pixel Experience, all good, all the steps to perfection and others, had microSD at that time so flash the boot.img by Fastboot. It seems to install the Boot.img in the Recovery TWRP partition, or something like that. Because I do not have the Recovery either, when I try to go to the recovery, the window "Bootloader Unlocked" appears, but it does not take me anywhere, only to the boot of the rom, it is something very strange and the truth scares me. I clarify: I can not access the Fastboot, nor the download mode, nor the recovery, because it does not.
There will be another way: ????
PLEASE IF SOMEONE CAN HELP ME, FIND ANOTHER METHOD TO ENTER THE FASTBOOT OR DOWNLOAD MODE, THE SOLUTION THAT WORKS WILL PAY ME WELL TO THE PROPONGA, PLEASE, I DO NOT WANT TO LOSE MY MOBILE, I BUY IT WITH A LOT OF EFFORT.
Last night I dawned on the boot logo, until it was completely downloaded and at this moment it continues to do so ... By GOD!
When trying to enter the Fastboot or download mode, it takes me here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image extracted from: https://www.tomshw.it
Then he starts loading the rom and stays there all the time .:
Image extracted from: https://www.tomshw.it
I can not access Fastboot, nor download mode, nor recovery, because it has disappeared. There will be another way to enter the Fastboot or download mode, because the phone actually woke up until I wake up today and was even charged. PLEASE.
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
ZestyManu said:
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
Click to expand...
Click to collapse
Hope this works for you @Yeriorlando. @gimpy1 had a similar issue when installing Havoc ROM. Part of the problem seems to be when installing the custom kernel?
gimpy1 said:
It was operator error (generally is) on my part, I'm sure. The only thing I did different that I can remember is installing the 9.0 boot image in twrp differently. I installed it in the recovery option first (intentionally, should not have), instead of ticking only the boot choice. I did not untick the recovery option (should have never ticked it in the first place, but I was trying to correct a problem on the ROM, and misread a post).
Click to expand...
Click to collapse
He was able to reinstall TWRP using fastboot.
gimpy1 said:
Thx, Chaz. I pulled out my printed instructions from your post, and once I was able to get my device recognized (that did take a couple of tries), reinstalling twrp was pretty easy.
I'm back in business thanks to you.:good:
Click to expand...
Click to collapse
IF you still can't after the suggestion at top, maybe @SGCMarkus or @runningnak3d have some tips?
Unless you have an H932, then if you get the error that: "Your device software can't be checked for corruption" then you have fastboot. It is literally impossible to have that message on a WTF rooted phone and NOT have working fastboot.
So, as @ZestyManu said -- make *sure* your phone is powered off. If you have to let, the battery die. Then hold vol down + plug in the USB cable (no need to touch the power button) and you will enter fastboot.
-- Brian
Thank you all. I have solved the problem in a super crazy way, to pure ADB, not fastboot .... Pure ****ing adb ... Hehehehe. Thanks to @ChazzMatt