I think it is time to say truth. LG540 cannot be recovered in original state, or at least bootloader. The first time you use fastboot, bootloader is changed and there is no way to back it to original state. For that reason you cannot flash LG540 with original KDZ from LG.
And that is fact that no one wont tell to you. All says that you got recovery mode, fastboot mode, but dont tell you that phone cannot be back to original state.
Now I know that, and it is to late for me.
Yes , you can changed roms via recovery menu, and that is ok, but all that roms are modded.
so be beware...
happy flashing
Hmm.. i can flash my first non-modded baltic rom (v20b_00.kdz) with my kdz updater.. in curiosity, i try the fastboot (camera+power) and recovery button but nothing happen.
So i guess it back to normal
Sent from my GT540 using Tapatalk
@Pepi74 Pretty sure you're wrong there, Bud.
When I first tried to put clockwork on my 2.1, I flashed a CIS 2.1 ROM that had fastboot, then I flashed clockwork from fastboot and that went great.
Then I decided to flash a stock Carphone Warehouse 2.1 ROM thinking I'd still have clockwork and fastboot - I DID NOT, THEY WERE BOTH ERASED BY THE NEW STOCK ROM
If you want to go back to stock then grab a stock ROM, put your phone into DOWNLOAD MODE and flash it with KDZ_UPDATER (if you had 2.2.1 on then wipe all data/chache from clockwork first) otherwise do a factory reset after you flash.
Try to make sure you know what you're talking about BEFORE you post.
I try that 10 times, and always have same result: after blue animation, LG stuck.
As I say, I can flash with fastboot modded ROM via KDZ, but cannot use original KDZ and flash it.
So I try many times before made this post to public
What application are you using to flash? There's no blue animation on the app you should be using.
Have another go with this app http://www.mediafire.com/?rj8dlhhp9ihm7ro
Put your phone in Download Mode (no battery, sd or sim - then hold vol - and plug in to PC). You see "Download Mode" on phone screen. Set app up as in picture and choose kdz file then Launch Software Update. Have a cup of tea. Profit.
{
"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 use KDZ updater just like you.
Blue animation is animation that show when android boot up: and after that comes white LG logo, and phone stuck.
All of tutorial I use says that KDZ updater must be set as
TYPE 3GQCT
on your picture is
TYPE CDMA
(so I need that you verify this settings)
Also phone mode is recommended as DIAG, and you set up CS_EMERGENCY
( so verify again that your setting is right)
On mediafire file you send me two files
boot.img and update zip.
How to flash this? ( via AMON RA) ?
Waiting for your answer , thanks for info!
P.S From where you get this settings? -links?
Sorry, I posted the wrong link - it's just to the KDZ_Updater but you have it already:
http://www.mediafire.com/?3hd4ao113lx8gq4
The phone should flash using this method even if you bricked it. I don't have the source of this method (maybe somewhere in the FAQ @modaco) but it saved my ass a few times and now it's the ONLY method I'll use to flash anything other than 2.2.1
You can either try it or not - I won't take offence
Open KDZ_FW_UPD as administrator by choosing "Run as administrator" in the right-click menu. Once it's open, set the type to "CDMA" and the mode to "DIAG". The people over at ******** will often tell you to set it to "3gqct" and "EMERGENCY MODE", ignore this as it will not work properly.
They say this way, so I will try it in CDMA mode
Try and retry
Yes, first time I pass this procedure got grey ANDROID logo, I think: that is that. But LG 540 stuck on that animation
So I give up.
Thanks one more time for you time.
pepi74 said:
Open KDZ_FW_UPD as administrator by choosing "Run as administrator" in the right-click menu. Once it's open, set the type to "CDMA" and the mode to "DIAG". The people over at ******** will often tell you to set it to "3gqct" and "EMERGENCY MODE", ignore this as it will not work properly.
They say this way, so I will try it in CDMA mode
Try and retry
Yes, first time I pass this procedure got grey ANDROID logo, I think: that is that. But LG 540 stuck on that animation
So I give up.
Thanks one more time for you time.
Click to expand...
Click to collapse
Hi Pepi,
your stock ROM got stuck because of the leftover userdata and/or cache from the "fastboot" ROM.
Before you flash the stock ROM via KDZ, you should erase userdata and cache (fastboot -w or wipe data/factory reset and wipe cache partition from recovery), go STRAIGT to download mode thereafter (must NOT boot into android) and then flash non-fastboot, stock ROM!
There is a whole tutorial on Modaco or here on XDA, but the above info should be enough to get you past the LG logo or Android animation...
Hope it helps...!
robber_t said:
Hi Pepi,
your stock ROM got stuck because of the leftover userdata and/or cache from the "fastboot" ROM.
Before you flash the stock ROM via KDZ, you should erase userdata and cache (fastboot -w or wipe data/factory reset and wipe cache partition from recovery), go STRAIGT to download mode thereafter (must NOT boot into android) and then flash non-fastboot, stock ROM!
There is a whole tutorial on Modaco or here on XDA, but the above info should be enough to get you past the LG logo or Android animation...
Hope it helps...!
Click to expand...
Click to collapse
What you explain I made minimum ten times without success.
I go to fastboot mode
fastboot - w
fastboot erase system
fastboot erase boot ( so I erase all I can erase as user)
Then reboot phone , go directly to download mode and flash with KDZ file. But no success
Flash is ok, but when finished, and rebooted stuck with first LG logo animation before grey ANDROID animation. I will be very happy when your process give me solution for my problem, but it is not
Opposite ( as I say before) when I flash with fastboot rom, every rom work without any problems.
pepi74 said:
fastboot erase boot
Click to expand...
Click to collapse
Never done that
All I've had to do is put the phone into download mode and flash with the latest stock rom in 3gqct & diag. Once it wouldn't boot up, so I flashed a V20B with fastboot, did the usual 'fastboot.exe -w' & 'fastboot.exe erase system', then flashed the latest Australian V20C rom, did a Factory data reset and was all good again.
If you can get a fastboot rom to work then do a factory reset from Settings > Privacy > Factory data reset. This wipes more than the fastboot method for whatever reason. After doing the fastboot wipe the phone always has the date and time correct where as the Factory data reset is reset to default values.
Anyway, what stock rom are you trying to flash?
Destroyer-XDA said:
Never done that
All I've had to do is put the phone into download mode and flash with the latest stock rom in 3gqct & diag. Once it wouldn't boot up, so I flashed a V20B with fastboot, did the usual 'fastboot.exe -w' & 'fastboot.exe erase system', then flashed the latest Australian V20C rom, did a Factory data reset and was all good again.
If you can get a fastboot rom to work then do a factory reset from Settings > Privacy > Factory data reset. This wipes more than the fastboot method for whatever reason. After doing the fastboot wipe the phone always has the date and time correct where as the Factory data reset is reset to default values.
Anyway, what stock rom are you trying to flash?
Click to expand...
Click to collapse
Any stock rom is ok, since I use english language. ( try 20B 20C Baltic 20D) - downloaded from LG web page.
And if you use fastboot -w and fastboot erase system, phone also reset to factory state ( language and date and time is erased)
So you suggest that I flash with fastboot ROM, then wipe data from factory data reset and then try to flash with stock ROM from download mode?
P.S Why not to fastboot erase boot?
every clockwork recovery has boot.img, so even erased I can bring boot back
pepi74 said:
So you suggest that I flash with fastboot ROM, then wipe data from factory data reset and then
Click to expand...
Click to collapse
And then flash a kdz version V20C or D with kdz_update in 3gqct & diag. Fingers crossed it works!
pepi74 said:
P.S Why not to fastboot erase boot?
Click to expand...
Click to collapse
Never had to do it, no problem with it if it doesn't do any harm.
Destroyer-XDA said:
And then flash a kdz version V20C or D with kdz_update in 3gqct & diag. Fingers crossed it works!
Never had to do it, no problem with it if it doesn't do any harm.
Click to expand...
Click to collapse
Try as you say, but result was same: stuck
I am the exact same as you mate. I also have tried numerous times to get back to a stock ROM and found it stuck on the second LG screen before the android logo. I have done ALL the steps, erased everything, tried everything. It's a bit of a bummer these stock ROMs.
pepi74 said:
Try as you say, but result was same: stuck
Click to expand...
Click to collapse
Crap!!
So the factory data reset worked, and the kdz flash worked but still stuck in the loop?
Sounds like wiping the phone doesn't wipe everything OR that a kdz_update crash does some damage some how. Never had a crash (touch wood) in kdz_update so maybe thats why I can go back to the LG stock AUS V20C rom.
I wonder if you guy's have a bad sector that the stock rom writes to. If this is true, I'm not sure how we can fix it.
keewanchoapsss said:
I am the exact same as you mate. I also have tried numerous times to get back to a stock ROM and found it stuck on the second LG screen before the android logo.
Click to expand...
Click to collapse
A kdz_update crash too?
Destroyer-XDA said:
I wonder if you guy's have a bad sector that the stock rom writes to. If this is true, I'm not sure how we can fix it.
Click to expand...
Click to collapse
I assume that many LG540 has "bad sector" in memory blocks ( I have two), but also found that programs are clever enough to NOT WRITE to those sectors, they are marked as bad ,and skipped when writes ROM. So I am sure 99.99% that bad sectors in memory are not related with function of stock ROM. Fastboot rom works ok, so if bad sectors are problem, I assume that fastboot sectors also have problems.
I know that phone must have part of memory that cannot be erased, and maybe fastboot rom writes something to that part.
Also mystery is also: why some users can flash stock rom without any problem, and many other cannot.
Destroyer-XDA said:
A kdz_update crash too?
Click to expand...
Click to collapse
Nope, didn't crash. It done the whole flash at the end it stated finished and then when my phone went to reboot it got stuck on LG loading screen. Although flashing the Clockwork 2.5.0.6 stock 2.1 rom works, but clockwork doesn't get installed. It's really strange.
pepi74 said:
I assume that many LG540 has "bad sector" in memory blocks ( I have two), but also found that programs are clever enough to NOT WRITE to those sectors, they are marked as bad ,and skipped when writes ROM.
Click to expand...
Click to collapse
Bad sectors aren't marked on Windows unless you do a long format (or search for them), it finds them and marks them. If you wipe the partitions the info has gone and if remake the partitions, windows will write to them unless you scan for them again and then you have trouble. Linux is the same, it doesn't scan for bad sectors by default when formatting so it will write to the bad sectors too, afaik.
Now kdz_update doesn't scan for bad sectors so it writes the whole image to to the drive so its possible that it is writing to a bad sector and that's why you have trouble. Possibly
pepi74 said:
I know that phone must have part of memory that cannot be erased, and maybe fastboot rom writes something to that part.
Also mystery is also: why some users can flash stock rom without any problem, and many other cannot.
Click to expand...
Click to collapse
Could be right about the memory, even with a kdz flash you still have some of your previous setup, that's why we have to factory data reset, so it doesn't wipe everything. If I was the foil head type, I might be thinking..........
Do the fastboot roms only write data to the already made partitions? Does kdz? I know kdz changes my button assignments if I flash a V20C > 20A.
keewanchoapsss said:
Nope, didn't crash. It done the whole flash at the end it stated finished and then when my phone went to reboot it got stuck on LG loading screen.
Click to expand...
Click to collapse
Not a crash but still with kdz rom. Hmmm.....
keewanchoapsss said:
Although flashing the Clockwork 2.5.0.6 stock 2.1 rom works, but clockwork doesn't get installed. It's really strange.
Click to expand...
Click to collapse
I didn't have recovery with the stock clockwork rom either, had to install it manually.
Destroyer-XDA said:
Bad sectors aren't marked on Windows unless you do a long format (or search for them), it finds them and marks them. If you wipe the partitions the info has gone and if remake the partitions, windows will write to them unless you scan for them again and then you have trouble. Linux is the same, it doesn't scan for bad sectors by default when formatting so it will write to the bad sectors too, afaik.
Click to expand...
Click to collapse
In that case mystery is much bigger. Fastboot ROM works without problem. So if you theory is true it looks like that fastboot ROMs are less sensible to memory errors ( bad block) then stock ROM, and that thing to me looks nearly impossible.
So answer must be in something that is not erased, and not in ROM and bad sectors.
Also even you erase all data from phone there is always left part it cannot be erased, so it is possible that information of bad sectors are stored in that place.
Related
Hello everyone!
Today I decided to change from Dalvik to ART. Phone restarted couple of times and was always stuck on "Android is upgrading". When it finally came to the unlock screen I unlocked it and then I got some error (Everytime I unlocked it). So that happened every time after I rebooted my phone. And after some time I think my battery went to 0% and I had to connect it and then I couldn't even get to the locked screen. Phone got stuck after Motorola animation and black blank screen appears.
I looked online to see what's the problem and saw that many people fixed this with flasing ROM, so I decided to do it myself. I unlocked the bootloader and tried to do some recovery with erasing cache and nothing works. I downloaded some ROMs includiding stock 4.4.4 and installed in command prompt with some fastboot commands like this:
fastboot-moto-windows.exe flash partition gpt.bin
fastboot-moto-windows.exe flash motoboot motoboot.img
fastboot-moto-windows.exe flash logo logo.bin
fastboot-moto-windows.exe flash boot boot.img
fastboot-moto-windows.exe flash recovery recovery.img
fastboot-moto-windows.exe flash system system.img_sparsechunk1
fastboot-moto-windows.exe flash system system.img_sparsechunk2
fastboot-moto-windows.exe flash system system.img_sparsechunk3
fastboot-moto-windows.exe flash modem NON-HLOS.bin
fastboot-moto-windows.exe erase modemst1
fastboot-moto-windows.exe erase modemst2
fastboot-moto-windows.exe flash fsg fsg.mbn
fastboot-moto-windows.exe erase cache
fastboot-moto-windows.exe erase userdata
Everything went smoothly but still when I turned on my phone it was still stuck at blank screen after animation.
I saw many other ways to do it including (ADB) but I'm noob at all this and tried something but I'm not sure which one to do cause there is so many guides.
Does anyone have any idea how to fix this?
I would really appreciate it!
Thanks!
candycornown said:
Hello everyone!
Today I decided to change from Dalvik to ART. Phone restarted couple of times and was always stuck on "Android is upgrading". When it finally came to the unlock screen I unlocked it and then I got some error (Everytime I unlocked it). So that happened every time after I rebooted my phone. And after some time I think my battery went to 0% and I had to connect it and then I couldn't even get to the locked screen. Phone got stuck after Motorola animation and black blank screen appears.
I looked online to see what's the problem and saw that many people fixed this with flasing ROM, so I decided to do it myself. I unlocked the bootloader and tried to do some recovery with erasing cache and nothing works. I downloaded some ROMs includiding stock 4.4.4 and installed in command prompt with some fastboot commands like this:
fastboot-moto-windows.exe flash partition gpt.bin
fastboot-moto-windows.exe flash motoboot motoboot.img
fastboot-moto-windows.exe flash logo logo.bin
fastboot-moto-windows.exe flash boot boot.img
fastboot-moto-windows.exe flash recovery recovery.img
fastboot-moto-windows.exe flash system system.img_sparsechunk1
fastboot-moto-windows.exe flash system system.img_sparsechunk2
fastboot-moto-windows.exe flash system system.img_sparsechunk3
fastboot-moto-windows.exe flash modem NON-HLOS.bin
fastboot-moto-windows.exe erase modemst1
fastboot-moto-windows.exe erase modemst2
fastboot-moto-windows.exe flash fsg fsg.mbn
fastboot-moto-windows.exe erase cache
fastboot-moto-windows.exe erase userdata
Everything went smoothly but still when I turned on my phone it was still stuck at blank screen after animation.
I saw many other ways to do it including (ADB) but I'm noob at all this and tried something but I'm not sure which one to do cause there is so many guides.
Does anyone have any idea how to fix this?
I would really appreciate it!
Thanks!
Click to expand...
Click to collapse
similar problem see here
if you can get to AP Fastboot flash mode its fixable see post #4 to reset (try this 1st)
http://forum.xda-developers.com/moto-g-2014/help/unmodified-factory-xt1068-froze-normal-t3024381/post58694698#post58694698
reefuge said:
similar problem see here
if you can get to AP Fastboot flash mode its fixable see post #4 to reset (try this 1st)
http://forum.xda-developers.com/moto-g-2014/help/unmodified-factory-xt1068-froze-normal-t3024381/post58694698#post58694698
Click to expand...
Click to collapse
Thank you for your reply!
I followed everything you posted on the other thread and it installed files successfully. But then again after animation it is still blank.
candycornown said:
Thank you for your reply!
I followed everything you posted on the other thread and it installed files successfully. But then again after animation it is still blank.
Click to expand...
Click to collapse
did you get any error messages if not that sounds like you need to wipe cache / data
can you boot to recovery to reset
or post #6 with modified script ( from AP fastboot flash mode )
will force everything to flash and reset
reefuge said:
did you get any error messages if not that sounds like you need to wipe cache / data
can you boot to recovery to reset
or post #6 with modified script ( from AP fastboot flash mode )
will force everything to flash and reset
Click to expand...
Click to collapse
I got 1 message about missing chunk.4 or something. In folder I have 0, 1, 2, 3 system.img_sparechunk.
I can boot to recovery and see 4 options (reboot system now, apply update from sdcard, apply update from ADB, wipe data/factory reset, wipe cache partition).
I already tried wipe data and wipe cache partition and still the same. Wipe cache finishes in just a second...
I already used that script in post #6.
candycornown said:
I got 1 message about missing chunk.4 or something. In folder I have 0, 1, 2, 3 system.img_sparechunk.
I can boot to recovery and see 4 options (reboot system now, apply update from sdcard, apply update from ADB, wipe data/factory reset, wipe cache partition).
I already tried wipe data and wipe cache partition and still the same. Wipe cache finishes in just a second...
I already used that script in post #6.
Click to expand...
Click to collapse
the modified is for lollipop only (dont worry it wont harm) just errors
i can do a kitkat if needed
reefuge said:
the modified is for lollipop only (dont worry it wont harm) just errors
i can do a kitkat if needed
Click to expand...
Click to collapse
Yes please.
I saw somewhere that I need to enable USB debugging for some things? How can I even enable it if I cannot access the locked screen?
candycornown said:
Yes please.
I saw somewhere that I need to enable USB debugging for some things? How can I even enable it if I cannot access the locked screen?
Click to expand...
Click to collapse
Done see other thread
no thats why its modified but you need to be able to put phone in AP fastboot flash mode by the volume down and power button method - no USB debugging required
down load 444 or 502 (not both) easy installer in my signature, then the CORRECT modified auto restore script, then extract both zip to SAME folder , usB cable in fastboot flash mode and run modified script
reefuge said:
Done see other thread
no thats why its modified but you need to be able to put phone in AP fastboot flash mode by the volume down and power button method - no USB debugging required
down load 444 or 502 (not both) easy installer in my signature, then the CORRECT modified auto restore script, then extract both zip to SAME folder , usB cable in fastboot flash mode and run modified script
Click to expand...
Click to collapse
I did as you said, download 4.4.4 and modified script into same folder. I ran the script and everything went fine, no errors.
But after it rebooted there was still blank screen after animation.
candycornown said:
I did as you said, download 4.4.4 and modified script into same folder. I ran the script and everything went fine, no errors.
But after it rebooted there was still blank screen after animation.
Click to expand...
Click to collapse
strange , DO you have the motorola device mangers drivers installed? (supplied in other thread)
did you watch phone screen as well - should have yellow confirmation text as flashes , purple shows problems
you definately have a xt1068 DUAL SIM phone?
reefuge said:
strange , DO you have the motorola device mangers drivers installed? (supplied in other thread)
did you watch phone screen as well - should have yellow confirmation text as flashes , purple shows problems
you definately have a xt1068 DUAL SIM phone?
Click to expand...
Click to collapse
Yes, I have the latest version of Motorola drivers.
SKU: XT1068
It has dual SIM
I watched the screen and nothing was purple, only yellow and on computer everything said OKAY.
I bought it on german site:
http://www.computeruniverse.net/en/products/90566676/motorola-moto-g-2-gen.asp
EDIT:
The phone can't be turned off. Everytime I turn it off it turns on again after 2 senconds.
candycornown said:
Yes, I have the latest version of Motorola drivers.
SKU: XT1068
It has dual SIM
I watched the screen and nothing was purple, only yellow and on computer everything said OKAY.
I bought it on german site:
http://www.computeruniverse.net/en/products/90566676/motorola-moto-g-2-gen.asp
EDIT:
The phone can't be turned off. Everytime I turn it off it turns on again after 2 senconds.
Click to expand...
Click to collapse
you have unlocked bootloaded status 3 in AP Fastboot Mode ?
did you at any time start a ota 5.0.2 upgrade or via any other method?
try running this in AP Fastboot Mode
reefuge said:
you have unlocked bootloaded status 3 in AP Fastboot Mode ?
did you at any time start a ota 5.0.2 upgrade or via any other method?
try running this in AP Fastboot Mode
Click to expand...
Click to collapse
Yes, I have status 3. I didn't upgrade to version 5 yet.
Do you recommend to try this fix that you attached first or version 5 that you sent me on PM?
candycornown said:
Yes, I have status 3. I didn't upgrade to version 5 yet.
Do you recommend to try this fix that you attached first or version 5 that you sent me on PM?
Click to expand...
Click to collapse
version 5 in pm now same as in my signature (both updated)
Yes I hope the 5.0.2 will sort things for you but no promises... if you have unlocked boot loader we should be able to go back to 4.4.4 (if you need to) otherwise you will be on 5.0.2
reefuge said:
version 5 in pm now same as in my signature (both updated)
Yes I hope the 5.0.2 will sort things for you but no promises... if you have unlocked boot loader we should be able to go back to 4.4.4 (if you need to) otherwise you will be on 5.0.2
Click to expand...
Click to collapse
Damn, it installed witout any problem I guess, but still stuck after animation.
Is this probably a defective phone? I am out of ideas what to do and thinking about repair shop.
candycornown said:
Damn, it installed witout any problem I guess, but still stuck after animation.
Is this probably a defective phone? I am out of ideas what to do and thinking about repair shop.
Click to expand...
Click to collapse
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
reefuge said:
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
Click to expand...
Click to collapse
In my case it wont even show globe for 5-10 minutes. After restore script finished on my PC and phone the phone restarted and went to animation like alaways. I didn't see any upgrading.
I will try now with TWRP.
reefuge said:
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
Click to expand...
Click to collapse
Ok, so now that I got TWRP finally something new showed up on my phone Team Win Recovery Project v2.8.4.0. I see many options (Install, Wipe, Backup, Restore, Mount, Setting, Advanced, Reboot). What should I choose here?
candycornown said:
In my case it wont even show globe for 5-10 minutes. After restore script finished on my PC and phone the phone restarted and went to animation like alaways. I didn't see any upgrading.
I will try now with TWRP.
Click to expand...
Click to collapse
when you boot into TWRP
select wipe
advanced wipe
then tick
dalvik
data
internal storage
cache
leave
system
usb otg
external sdcard
swipe to wipe
press (left) home icon
reboot
system
do not install
reefuge said:
when you boot into TWRP
select wipe
advanced wipe
then tick
dalvik
data
internal storage
cache
leave
system
usb otg
external sdcard
swipe to wipe
press (left) home icon
reboot
system
do not install
Click to expand...
Click to collapse
Did all that and got this:
Wipe Complete
Failed
Full SELinux support is present.
E: Unable to open '/cache/recovery/.version'.
MTP Enabled
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
- - Dalvik Cache Directories Wipe Complete!
Wiping data without wiping /data/media ...
Done.
Wiping internal storage - - /data/media...
Updating partition details...
E: Unable to stat '/data/system/++
/
1
'
... done
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
rassle said:
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
Click to expand...
Click to collapse
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
im actually trying with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml which has the title of XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B
i do have problems of finding stock roms as most links are pointing to sbf droid developers (cant post link due to beeing new) which is dead for me.
ive used shadows mirror list, but its only showing non-4.1.2 versions for me. however, im not quite sure which firmware was one the phone before *sorry*
by commands of the xml file u mean the xml file which is contained in the "firmware" downloads for the XT890?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
rassle said:
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
Click to expand...
Click to collapse
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Hazou said:
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Click to expand...
Click to collapse
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
rassle said:
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
Click to expand...
Click to collapse
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
rassle said:
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
Click to expand...
Click to collapse
Good that it worked. The message will remain there. I don't know how to fix that issue. But I don't think it is a huge issue, but its annoying.
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
bump pls
even bad news is appreciated
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Hmm.. does phone in TWRP works like USB storage?
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"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"
}
swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?
vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.
swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?
swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.
redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.
Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?