Hi folks,
My phone is unlocked & rooted and it only starts showing the android logo after I updated with the official updater in the phone, the december update.
When I want to flash it with the stock rom in fastboot mode, according to this (https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548 ), the flasher says just"can not found file flash_all_except_storage.bat"
I have no idea what to do.
Can anybody help me?
Don't want to throw away another 200 dollars
Thank you,
Michael
Youre missing a file in the stock rom
ProchyGaming said:
Youre missing a file in the stock rom
Click to expand...
Click to collapse
O rly?
I extracted the stock rom now with 7zip because it was a tgz and extracted the stock rom.
Now I used the flash_all.bat but it gets stuck at 'Writing system_a'.
Maybe because of lack of space.
ADB doesn't recognize my phone. Fastboot does. Can't go into recovery mode.
Partition table seems to be ****ed up. Any ideas? :/
OK, for all people with the same problem:
I used the linux scripts on my linux system and it booted / worked perfectly.
No idea why the windows crap didn't work.
Hope to have helped you
I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.
zeyaan said:
I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.
Click to expand...
Click to collapse
{
"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"
}
Related
hello. first of all, i am a complete noob. although i will be glad to learn, i guess i will need slow explanations...
so, i have rooted my defy plus 2.3.6 , then installed 2nd init bootmenu and took a backup. then tried to flash this and ever since im getting only the moto splash screen and a reboot over and over.
ive tried looking all over this forum for a solution... tried doing custom recovery but it says no such file or directory, tried doing a stock recovery and it gets me to android system recovery. i also tried flashing different roms on my sd, using the android system recovery, but it says signature verification failed
even did a factory reset .
am i doomed to see this logo till the rest of my life?:crying:
The solution should be simple, you must flash your phone using RSDLite again.
your clockworkmodrecovery-menu is gone with the factoryreset in stock-recovery.
So you must flash again the rooted SBF for the defy+, installing 2nd init bootmenu and choose the right flashable zip for your device.
A flashable.zip for a samsung galaxy s2 will not work on a defy+.
in which stage should i connect my droid to the computer ?
usually when i connect it , RSDlite dont see it.
can you post a link to some stable flashable zip for defy plus?
You can use this:
http://roms.custom-android.de/counter/click.php?id=86
it is the white Rabbit Plus Edition v1.6.
To flash a brand new SBF you must enter the bootloader, then rsdlite should recognize your device.
animated image how to enter the bootloader:
{
"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"
}
wow!! i guess it was nothing for u, it was everything for me!!
u literally saved me! :victory:
(ok, ok at least my phone... )
really, the thanks button is to small..:fingers-crossed:
can i do something else?
oh and another thing , will the defy+ work with miui?
or alternatively is there a rtl fix for cm7 ?
You can also try this ROM:
http://forum.xda-developers.com/showthread.php?t=1543272
but AFAIK MIUI CM9 (V4) lags a little bit more then CM7-Built, or cyanogenmod CM9-builds.
AFAIK, there not really full ported MIUI for the defy+.
The WhiteRabbit emulates the miui-Style in the best way.
hello to all xda members
in the past i update a gt540 (1.6) to 2.1 and then to cyanogenmod, this come new from store with 1.6 and never have a problem with this phone.
Now i buy a gsm unlocked gt540 wich come from store with 2.1 and then i tried to update to 2.1 stock fastboot rom with kdz updater(using the same guide that i used in the first phone), the problem is that the process was stopped and the Phone was COMPLETELY bricked.
The only way to come back to life was a complex conection(jtag) with a box named "Medusa box", but the problems no stop here, when the phone turn on there is no way to grab signal until i used a lge oficial box to repair NVM and then unlockconfused: the phone was from factory unlocked) again the phone.
i need install cyanogenmod, bacause the phone is actually no fully working since enach time, this said some like this."process android was stoped," an others like this saying a process o app stop working.
i need your help to now how update, or if the phones that come from factory with 2.1 use a diferent way to update.
the photo is my actual rom(2.1 oficial rom)
{
"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"
}
Need to think this through...
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
XiproX said:
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
Click to expand...
Click to collapse
Thanks this finally works.
hi,
with fastboot mod, my phone d'ont won't to pass the cyanogen blue cross at the first boot.
So, i install the clockworkrecovery.img, i download the SDSL rom for recovery, and it was quickly and secure installed.
*##### EDIT #####*:
Who would have thought that running Windows with VMWare Fusion on Mac OS X could mean that Flashing tasks aren't always a possibility... Tried on a nearby Windows computer and it worked completely fine..! How disappointing, sorry the waste of post, could a Mod please delete this.
Cheers again.
_____________________
Hello all.
I have a Galaxy S4 GT I-9505 which, to date, has shown me that it seems to be impossible to revert it back to stock firmware, of any kind...
I have tried numerous different stock firmwares and every single one has failed. I came from a Rom called 'Foxhound' and was a newly released 4.4.2 at the time, so I'm guessing KNOX has done something to the bootloader which has deemed my device in limbo - to my knowledge.
The thing is, I've come across a leaked 5.0.1 firmware for this device, so I thought I'd download it, only to notice that the Odin flash file wasn't a single TAR file but a series of other files that correspond to the functions of Odin.
From this point on, I decided to try and flash the Bootloader file by itself, and that WORKED. Of course, the only progress I was getting from this was the basic boot logo at the beginning of powering on the device.
Seeing as I was unable to boot into recovery, I thought I'd try and download an Odin flashable CWM Recovery, and this also WORKED.
The thing is, whenever I attempt to flash a full Rom through Odin, it will go through the inevitable error that it does with all attempts.
Here are some images:
{
"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'm beyond frustrated by this as I can't deem the phone usable until I have it up and operational, and it is basically worth nothing in this state.
I would be endlessly grateful if someone would be able to point out what the possible issue may be, I would be beyond thankful!
Best regards,
Try to use Odin 3.09
Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"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"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app
Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken
[SOLVED] I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and now i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
{
"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"
}
SOLVED
daverob79 said:
I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and no i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
Screenshot on imgur.com/gnUBeXS
Click to expand...
Click to collapse
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
daverob79 said:
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
Click to expand...
Click to collapse
Ok, so I was able to flash this rom and boot the tablet. But when i get the OTA the tablet crashes...
The OTA was YT2-1050L_USR_S100192_1511191319_WW52_ROW
Now trying YT2-1050L_USR_S100081_1507241439_WW52_ROW, will update with results
Can it be that the OTA did not have all the right files. Or did the root process do something so that I can only flash stock roms?
I am really not getting any wiser on this intel world. Only been playing with Samsung, Nexus(LG/ASUS) and HTC
Any thoughts? Anyone??
And I can't post images, sorry for that :c
forgot this,
Thanks ionioni
after you flash remember to set your region code before taking any ota's (on the first Android boot go to Contacts and in the search contacts box input ####59930# and if it shows a two letter country code then you're good to go, if it shows 'unknown' then you need to set a country code, input in the same box ####6020# and chose a country, yours or a close one, tablet will reboot)
Click to expand...
Click to collapse
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
corasman said:
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
Click to expand...
Click to collapse
I did
Now I have my tablet back!
Seems like there is a big difference between the ROM's (the YT2_1050L_USR* files)
Maybe we should have a tread with all the different ROM's?
I found this on Androidfilehost: Link to downloads for Lenovo Yoga Tablet 2 by ionioni
But how do you see the difference between different roms. Many are big files even if they are not stock roms (with radio, droidboot, bootloader, bios etc)
Now I have 1050L_S100255_160113
Is this the latest ROM?
I think the differences are in the file names...after YT2 it tells you which file is for which model.