First off, I'll be brief, but I'm new on the site. I've been around looking at the forums here and there which helped me to previously root my Atrix.
I had intended to return this phone, but it's watermarked which sucks. Whatever, there's nothing I can do about it now. For fear of it not being returnable I decided to wipe the Atrix and unroot the phone. I first ran aRoot to unroot the phone. Everything worked to basic perfection unrooted. I deodexed back to 1.83 to get rid of GingerBlur, which it did. I did notice, however, that the phone would still boot into Tengar's CWM Recovery Mode when plugged into a wall charger while powered off. In a fit of absolute stupidity, I formatted everything that it is possible to format while in the CWM Recovery outside of my microSD card. Now when I reboot the phone it sticks on the "Dual-Core Technology" with Moto logo screen. No boot whatsoever.
After freaking out for a good hour or two I tried a couple of things I saw on this website because I can get into the general phone recovery (by holding down the volume button). All of them have been no-gos for me so far.
The recovery from a soft brick on the wiki gives me "Cold-booting Linux/ Reading ODM fuse: 1" when using Early USB Enumeration and sits on that indefinitely which takes out ADB. I can boot into Android Recovery mode, but, as has been noted on that topic, you can't load any update.zip files as the microSD card is not mounted. I also tried doing a wipe data/factory reset via Android Recovery but that's a no-go as well. On the bottom left it does say "E:Can't open /cache/recovery/command" in AR. I thought about flashing back to 1.83 or older using RSD-lite, but I get "Battery is too low to flash" every time when going into RSD mode.
Outside of these problems, my phone will turn on when plugged into a computer, but only to the same screen mentioned earlier and it takes nearly and hour after the charge has been (presumably) completed. The phone will not charge via USB wall charger - instead the phone turns on. I have no flashing red LED or any other warning messages nor can I turn the phone on without it being plugged into a USB cable.
When AR is run for factory reset:
.Performing BP clear...
.E: open mdm_ctrl ok
.E: bp status before bp power down 0
.E: (0,success -1, failed, 1, panick), return result: 0 after BP shutdown....
E: begin BP power up.....
E: reture value of bp start up:-1
E: bp status after bp power up 4
....E: from flash to normal mode
....E: open dev
E: engine init finished
E: Successfully wrote 13 bytes.
E: Transferred 13 byte(s) CMD opcode = 0x0012 to aux engine succeeded.
E: write finished
E: Attempted to read 12 bytes and read 12 bytes.
E: Successfully read 12 bytes.
BP clear complete successfully.
Formatting DATA:...
Formatting CACHE:...
Data wipe complete.
After which I let it reboot. It sits there at the logo, still, no matter how long I leave it plugged in.
As a side note, last I remember, my phone was set with USB debugging on and to be a Mass Storage Device.
Please, I'm desperate right now. This is going to be my only phone for the next two years, whether I like it or not, and I'd like to keep it (besides, I do quite like it).
Post deleted
Sent from my Motorola Olympus using XDA Premium App.
i did not understand quite well your situation but in a desperate time this is what i would do:
to bypass the low battery, you need a usb cable:
open like the picture
{
"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"
}
insert the red one between battery and its connector on the phone (the + on the battery will tell you the correct "slot" ) battery needs to be correctly inserted.
plug to the pc
the phone will think it's fully charged.
then plug a normal usb cable to pc and phone enter rds mode and let the process begin, full sbf (not service) advised
let it go
Well, as helpful as that was, the cut-a-USB-to-charge trick didn't quite work for me. Might anyone else be able to help me? My phone is as dead as a door nail atm.
same here...
Me too, have a very similar problem, but not because of flashing ( I think so ) ..
Chronology : have use phone regularly with Froyo, rooted, no unlocked bootloader yet, no micro SD card ever inserted, can access internet with small download speed.
The problem arise (as per I remember correctly),
first, I install Calc-P (sideload from androiddev dot orkitra dot com) , install then use it, no problem ..
second, update Android Assistant from market, install and use, no problem
third, download then install Smart Taskbar (com.smart.taskbar)
download went fine, but during install, it takes like forever to finish, AND it doesn't!
unfortunately, my battery on that time was dried off, and the-install-takes-forever just died.
after a full recharge, I turn on, and used the phone ok for a while, until I realize there are some app (from market) that I don't regularly use, so I decided to uninstall it.It also, TAKES FOREVER with nice black&white rollover progress bar.
I think, something went wrong, so, panickedly, I turn off the Atrix.
And now, just stuck on Rethink Possible bootscreen, no where else.
-tried android recovery : no go
-tried android boot (no bp) : no go
-tried fastboot : no go
Someone, please, how to solve this.
Problem solved by wiping all data and apply pie crust (from navalynt) onto those already crispied gingerbread ..
Related
First off, I would like to say sorry if this is the wrong section to post this. I'm a total noob
Secondly, I don't have a Vibrant, I have a Samsung Galaxy S 4g. I couldn't find a specific thread for my phone but I was guessing I should post it here because I thought that they were pretty close? The Vibrant being sgh-T959 and S4g is sgh-T959V, so I'm hoping I can get some help here.
I've literally spent about 16 hours or more trying to fix my phone (2 days).
Here's what happened:
I flashed my phone with Heimdall following instructions here at this forum: http://forum.xda-developers.com/showthread.php?t=1358498. At the very bottom of the first post is the download section and I downloaded the 2nd choice which I believe is "Download KJ1 Kernel Stock Rom with Bootloaders". I only flashed my phone because it was having problems.
I went and flashed my phone and it worked! It was working fine until I went to RootExplorer changing permissions on a txt file and my phone froze (I don't think changing permissions on the txt file was the problem). So I reseted my phone by holding the power button down until it boots up and then I got stuck in some kind of boot loop (where the phone keeps rebooting after samsung galaxy logo). So I thought the only way to get passed this is to reflash the phone with the same procedure I did earlier.
I put the phone in download mode and went on with the flashing. For some reason it got stuck and it wouldn't finish. On the Command Prompt, it got stuck at this:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\modem.bin]
And on the other window (Heimdall's window) it got stuck and shows this:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
So what I did was close both windows and tried again. This time my computer couldn't recognize my computer. Then I turned my phone off and tried to go back to "Download Mode" but instead, it showed a "Phone with dotted lines through this yellow triangle and into a computer". So I turned the phone off again and tried and tried and kept trying to put it into download mode but couldn't get it to work. It kept showing the phone, triangle, and computer. Although I did realize that my computer can still recognize my phone at this state.
I tried using ODIN but odin couldn't recognize my phone. Went back on Heimdall and that still recognizes my phone! I was feeling hopeful but whenever I kept trying to reflash my phone, it keeps getting stuck at the same spots that I mentioned above.
Can someone, anyone, please help me with my situation? I'm way to broke to buy a new android. This phone is incredible and I really would want to get it up and running again. Is there a way I can get passed this?
I know this is a lot of time reading this but I would highly appreciate anyone that can help! Please and Thanks you!
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
"SOFT" BRICKED WHILE USING ODIN?
{
"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"
}
If you are getting a "Phone.. ! ..Computer" image (seen above) when booting phone, yes, you are bricked but it is reversible! Just follow these steps...
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Woodrube said:
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
Click to expand...
Click to collapse
Thanks for the Galaxy 4g threads! and yeah that does look very familiar its just that I did everything I can to get into download mode but I can't get it to work. Thanks again for the threads!
I remember when I was a noob(no pun) the same thing happened and couldn't get it to do anything for like 4 hours. I think I opened odin took battery out, installed usb to computer, hooked usb to phone, pressed volume up and down simultaneously and installed battery without letting go of the volume buttons (I'm not sure if youll see dl mode on phone),pick your .pit/.tar files and flash away even without the COM showing
On the post above mine I think step 4 and 5 should be reversed
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
Hi All,
My son brought his Tablet to me yesterday and told me "It's not working". I looked at it and it was stuck on the Lenovo screen. I booted into recovery but it looks like its messed up 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 of issue -> ibb.co/1zCLyYr
After some probing my son tried to unlock it and load a rom, then restore stock rom and it was the last that caused the issue.
Now generally being able to get to recovery is a good thing but in this case it looks completely messed up and nothing will mount including the SD card.
It looks like adb is no longer enabled, it is not rooted and USB debugging is no longer enabled.
So it says
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache
And so on.
This means I can't actually get to the SD Card with any update on it if I go to apply update from sdcard there is nothing showing in the sdcard directory
Have tried the following
- Apply from ADB (Device does not connect)
- wipe/factory reset,
- wipe cache
- reboot to bootloader
I can't get into any download mode either.
I did get it at least to make a mounting noise temporarily in Windows 10 but couldn't actually get to it or browse from there and haven't been able to repeat this.
Just wondering if there is anything I can do, or whether I should just forget it, surely there is some way to connect to it.
Cheers
Dan
Interestingly I plugged it into my mac and first it booted to a charging screen which hadn't happened last night.
Also if I leave it plugged into my mac for a little while Android file transfer eventually pops up and tries to connect but then says "Could not connect" but there is some life there at least.
A little more probing and I plug it into my Ubuntu rig and it starts to be recognized as Android but then get "Cant load MTP Device" if I try to browse it.
Looking into dmesg gives me
idProduct=78e8 (This is a Qualcomm powered device)
It then tries to mount it all but ends up mounting it as a Lenovo CD-ROM.
I can't seem to probe it past that, thinking its a futile effort but hoping for a miracle
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Silvertails said:
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Click to expand...
Click to collapse
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
jwoegerbauer said:
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
Click to expand...
Click to collapse
I cant do any kind of stock recovery, sideload is the closest I can get to anything, I think he must have put a different rom in there that has stuffed it up.
Is there anything I can do any steps I can take?
Windows won't recognise it so the QPST/QFIL method won't work
any steps or help would be appreaciated I have trawled every thread I can find here an across the internet
@Silvertails
ADB Sideload is a special mode that internally makes use of / runs Android's recovery binary ( AKA Stock Recovery ).
You test whether this mode is ready or not by simply running on PC the commands
Code:
adb devices
adb reboot recovery
If successful then you in Recovery select option "adb sideload" and on PC run
Code:
adb sideload <FILE-NAME.ZIP>
There's a very good thread on XDA here that deals with this model and recovering from bricks.
https://forum.xda-developers.com/thinkpad-tablet/general
Finally got this to work.
Ordered a cable that could get me into deep download mode as jumping the pins on the mobo was not working, the cable didnt get me into download mode, but what i discovered was that if I uninstall it being recognized as a CD ROM and messing about a bit I eventually got it to recognize as an Android Bootlader Interface using the lenovo drivers. I managed to use fastboot even though the device wasn't properly recognized to install TWRP. I got a success message and managed to reboot into TWRP recovery. The device then mounted as Lenovo but a different one, but at least it was mounting.
I still couldn't copy anything over to it, so I put the OTA default ROM on an SDCard and managed to get it to install from there and update to latest versions, and now its all working again.
greetings. i need help with my lg v10 f600s which is now hard bricked. the story go so, when i go the phone . it was running on marshmelow no issues or problems.then i installed termux and when i wanted to update or download packages it kept on giving me errors.o googled around and found out it had to o the it no longer been maintained on mm software.so i searched around and found an update for the phone to nougaout firmware, so i downloaded it and updated the phone and thats when all my problems started .first my speaker phone stoped working , the major issue was the phone would randomly turn off at 40, 50, 60 percent charge.so i donwloaded the stock mm firmware to downgrade back to mm used lg up but it would not work and kept giving error.tried several other lg flash tools to no avail. then so a video about using qfil, then i built a qfil flashable firmware and managed to get the phone in to edl mode but while flashing i got these errors
{
"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"
}
then i switched to miracle tool and kept gettint this error even with the system.img file present
all throug this process my phone was boot up but all of a sudden when i tried turning it on ,it would not boot up or charge again. i can still enter the edl mode by shorting test points, and also the pcd would heat up when i enter edl mode.pleas how do i solve this.
The V10 was a flagship with known bootloop & heat issues. LG extended it's warranty by 2yrs. Try https://duckduckgo.com/?q=xda unbrick v10
ok thanks let me check it out
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
ǀcey said:
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
Click to expand...
Click to collapse
tried the link but could not find any solution, and i cant clear cache even if the phone was on because i had booted in to recovery but there were no cammmands, and it does not boot into fastboot mode.and i am in cameroon so ebay is not an option.this phone is realy giving me a headache and right now i am not in the position to buy a new PHONE NOW.if only i had access to a box that would make things easier .there is also one thing i noticed when i disassembled the phone it written on the board F600L__EAX66751701_1.1_MAIN. I THINK THIS MEANS I ACTUALLY HAVE BUT AN F600L AND NOT F600S.BUT THEN ON LGUP IT SHOWED F600S
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
ǀcey said:
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
Click to expand...
Click to collapse
i managed to flash all other partitions using MIRACLE except the SYSTEM partition by editing the RAWPROGRAM0 XML file and removing the line of code that enables flashing SYSTEM partition which got rid of the error "CAN NOT FIND SYSTEM.IMG".now i am trying to flash the system partition alone
i am getting "sahara_rx_data:194 unable to read packet header.only read 0 bytes"
using qfil
finally flashed the system partition using MIRACLE TOOLl but phone wont still turn on.i think it realy is an f600l and not f600s.i will build a different firmware using the f600l kdz and flash it see if that works
greetings i have flashed the f600l firmware but still no change phone is still dead. even flashed the firmware dump that i took before the phone got bricked but still no change.and the firehose file only works with miracle tool when i use qfil it keeeps given me errors.pleas can some one help me with a firehose file that will work with qfil
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?