Phone Bricked after JB update - Motorola Droid 4

Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.

Lightofdark said:
Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.
Click to expand...
Click to collapse
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.

kwyrt said:
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.
Click to expand...
Click to collapse
I replaced the system folder on my phone by the one of lum's rom with file manager into safestrap recovery (not smart i know). And I already try to reflash the update in the recovery but it didn't work. I'll have to wait untile JB fastboot files comes out and use my old Xperia mini pro
EDIT : Ok, i can update my phone to JB with recovery, but then the phone boots on AP flashboot automaticaly and says "flash failure"

You deleted the stock ROM and copied over the files from my ROM by hand?
That's not going to work as it will also delete safestrap recovery as you have found out.
The JB OTA update won't install as it is a patch that only applies to the stock ICS ROM.
Attempting to downgrade to the ICS fastboot files will perma-brick your phone. Some partitions are safe to flash, some can only be upgraded. Fortunately the system partition is flashable without that nasty issue!
However I've had a look at how Droid4utility actually flashes them and it seems it is possible to flash just the system partition in fastboot using:
moto-fastboot flash system.img
I have dumped the system partition from my phone and am currently uploading it. It will take an hour to upload and I'm out for the afternoon. Edit: It's here: http://d-h.st/oXt
You'll need Fastboot and the Motorola USB drivers
Install the USB drivers.
Decompress the system.img file you downloaded. Put it in the same directory as moto-fastboot.exe.
Ensure the battery in your phone has lots of charge.
Boot the phone into fastboot by holding down both volume buttons and pressing the power button.
Choose fastboot by pressing the vol down button until fastboot is highlighted, then press vol up.
Connect your USB cable.
Run moto-fastboot flash system.img
Run moto-fastboot reboot
Note: I have not tried this on my own phone, and I hope I never have to. It should work in theory.

when ever i have used moto-fastboot, i had to use 'moto-fastboot.exe' to get it to work
Sent from my Clear using xda premium
---------- Post added at 11:33 AM ---------- Previous post was at 10:38 AM ----------
not sure what exactly what you will need to flash for jellybean to unbrick
download
update.zip for your device and system version
moto-fastboot.exe mediafire
instructions
1. Enter android recovery and do a wipe data/factory and cache
2) Then reboot device to fastboot mode.(make sure to have all motorola drivers installed on your PC)
3) move the update Zip and the MOTO-FASTBOOT to a folder (ex. c:/Root)
4. unzip files
5) Open the CMD, and enter the these commands.
cd/
cd c:root
moto-fastboot.exe flash system system.img
moto-fastboot.exe reboot
also try renaming patch/boot.img.p to boot.img
moto-fastboot.exe boot boot.img
moto-fastboot.exe reboot
do not let battery die, phone requires software to charge battery,
if battery dies you will need a
TBH’s Motorola Programing Cable

The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.

Lum_UK said:
The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.
Click to expand...
Click to collapse
How can i know if the phone does charge or not ?

turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs

sd_shadow said:
turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs
Click to expand...
Click to collapse
when i plug the cable it automacialy boot in AP fastboot, it doesn't seems good

what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....

Well annoyingly, that file I was trying to upload for you... Windows 8 decided to go into sleep mode before it had finished uploading, starting again.
I'm also happy to try and dump any other partitions that may help, if someone can tell me how to do it.

sd_shadow said:
what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....
Click to expand...
Click to collapse
AP Fastboot Flash Mode (S) (Flash Failure)
0A.77

does android recovery have, this phone has been rooted code
qe 1/1
Click to expand...
Click to collapse
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
{
"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"
}

Well the system image is finally uploaded if you want to try it
http://d-h.st/oXt

sd_shadow said:
does android recovery have, this phone has been rooted code
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
Click to expand...
Click to collapse
Thanks for your advice, but I live in France, and there is no Verizon store here.

Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.

Lum_UK said:
Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.
Click to expand...
Click to collapse
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), with at the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"

Lightofdark said:
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), and a the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"
Click to expand...
Click to collapse
Well it was worth a try. Now you'll just have to turn it off and hope the fastboot files show up soon

ok, so I'll wait. Anyway, thanks a lot for your help and your time.

Hello,
I was lead here because I'm having a similar problem... though not nearly as bad as the OP, it would seem. I managed to brick my system partition by trying to restore a nandroid of a working JB system partition in safestrap to stock slot to resolve some other errors in the install precipitated by a bad restore from Titanium.
Good news is that safestrap still works, and I can boot to any other slot... just not stock. When trying to boot stock, after the safestrap screen, I just get a black screen... it makes the *droid* sound, but screen stays black and nothing happens. No logo or OS appears.
I'm wondering if it might be worth a try to flash your system.img, or if I should leave it alone and run on safestrap until fastboots show up (which is hopefully soon)?
Thanks!

Related

[Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!

thread outdated ! please user romracer's http://forum.xda-developers.com/showthread.php?t=1204500
Hi ALL,
This is the recovery.img build for Unlocked AT&T Atrix 4G.
You can flash this direct to the recovery partition for a unlocked device, no more AC charger!
Thanks Koush and other devs who are working on the original cwm recovery.
enjoy porting CM7!
this is under developmet ,please use at your own risk! but every release will be tested first.if you like my work. buy me a beer
have fun.
Updated:GMT+8:00 06-30 11:20am
filename: recovery-en-goapk-0630-1029.zip
add backup and restore pds( backup tested,restore didnt test.)
add Internal SD card Support (nandroid and choose zip from internal sdcard)
should add a restart adb server int the menu in next version.
Latest Download:
View attachment recovery-en-goapk-0630-1029.zip
{
"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"
}
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.
GMT+8:00 2011-06-25-22:25 Update again:
Important Update!recovery-en-goapk-0625-2034.zip
fix wipe format and backup restore
latest: View attachment recovery-en-goapk-0625-2034.zip
GMT+8:00 2011-06-25 03:38 Update:
fix format data and cache
please update to latest build.
another fixed!
please update.
and every other thing should work as it should。
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Linux:
unzip recovery-en-goapk.zip to you home
mot-fastboot flash recovery ~/recovery-en-goapk.img
mot-fastboot reboot
pics:
Downloads:
2011-06-24-16:10 GMT +8:00
View attachment recovery-en-goapk.zip
2011-06-25 03:38 GMT +8:00
View attachment recovery-en-goapk-0313.zip
HERE IS THE EASY GUIDE:thanks Paschalis !
I had the prev version of CWM, and i wanted to update to the latest, using moto-fastboot instead of fastboot..
It's very easy.. So i wrote a little guide.. Dont blame me.. Its for new guys like me!
Btw will any future update of CWM, have adb enabled?
eg If we messed up with framework or anything else can cause a soft-brick, then recover using backup files..
Step-by-Step
How to install on Windows with moto-fastboot
1) With Root-Explorer go to: /system/etc/ and remove: "install_recovery.sh" file
2) Download moto-fastboot.rar, and latest recovery recovery-en-goapk-0630-1029.zip
3) Extract contents of moto-fastboot.rar in C:\Windows,
and content of recovery-en-goapk-0630-1029.zip in C (for example).
4) Get your Atrix in FastBoot:
................................ a) Turn it off
................................ b) While turning it on, press VolumeDown key
................................ c) Press VolumeUp key
................................ d) Connect your Atrix to your PC using usb data cable
5) Open a cmd (Command Prompt)
6) Enter following cmd commands:
............. a) cd C:\
............. b) moto-fastboot flash recovery C:\recovery-en-goapk-0630-1029.img
............. c) moto-fastboot reboot
7) Thank Paschalis for this guide!
Click to expand...
Click to collapse
original post on http://bbs.goapk.com/thread-2874929-1-1.html
please include this info when you post this on other forums.
Holy freakin Hell!!! Thanks!!! Good to hear from ya!!!! Its like xmas around here in june!! LOL
Great to see this so soon. I cannot wait for a fully functional version! Glad to see you still lurking around here tenfar, thankyou for this, as well as koush and all the others (if any) involved in making this happen!
How To: Get into CWM Recovery
Using ADB:
- adb reboot recovery​
Using buttons:
- Hold down power, downward volume buttons until you see "Fastboot"
- Use downward volume button to click multiple times until you see Android Recovery
- Then, press the upward volume button​
Thanks! Tenfar excited to put it to good use!
omg today is going nuts! only if i could get gingerbread lol
Any chance for the source? Or at least say how you got it working?
could i unlock simlock my phone with flashing ur file?
lechicuong said:
could i unlock simlock my phone with flashing ur file?
Click to expand...
Click to collapse
No... 10char
i flashed this recovery via fastboot but any idea how to get in to recovery?
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Daniel_GB said:
i flashed this recovery via fastboot but any idea how to get in to recovery?
Click to expand...
Click to collapse
hold vol down while powering on. press vol down to scroll the choices and vol up to select android recovery
rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)
lol...positive..
Just to let you know I flashed the 1.8.3 sbf after unlocking and then tried to flash this and met with failure.
I then ran the unlock sbf again (only) and it flashed successfully. Perhaps flashing a previous sbf does "re lock" (at least partially) the phone?
rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol
Bakano said:
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)
Click to expand...
Click to collapse
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..
rickriego said:
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..
Click to expand...
Click to collapse
No I did the same thing and got the same error. you gotta reflash the unlock sbf to fix it. everyone is right.
You can enter recovery mode with "adb reboot recovery" too!
jruweaver said:
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol
Click to expand...
Click to collapse
yep...flashed to 1.83 like you. i'm gonna charge up and try the steps u took..thanks..

stuck at fastboot

Hey i am stuck in fastboot (going for a week now) and i kinda think it's dead i did that full wipe script and now it won't boot into anything i can do bootloader (my bro told me it can be flashed by there but i don't even know also i can't get into hboot due to the camera button being stubborn) so might as well ask here since he's at my cousins house for now and also how can i flash zip files? like the kind that aren't .img? just for details every time i try to flash via fastboot it either says unknown partition or cannot load blah.img maybe it's something i did wrong? i got adb/fastboot setup with the sdk and stuff but that's as far as i can get .
also i can't use adb (should be obvious by now).
can you access recovery mode? holding home+power?
I can try but don't guarantee success in doing so because of something i did in fastboot by mistake in trying to fix it ( ) unless there's a way of re flashing ra's rom or something there's no way i can get recovery to work again.
edit why don't they have those windows to phone flasher just like the hd2's have them that way i would have had it fixed by now .
Probably you should read a bit in this post.
If you are in fastboot, you can do almost everything with your phone.
1.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
and your phone is clean.
2.
Code:
fastboot flash recovery <recovery.img>
and you have a working recovery.
3. you can decide how to continue ...
whenever i try to flash it(at last step at the instructions at top), it keeps saying error: cannot load 'Recovery.img' file ,weird , i am using ra's recovery has recovery.img , don't know why it's not letting me flash it
edit even has the original name it won't load
you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img
AndDiSa said:
you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
Because a button is not good enough here you go
{
"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"
}
for showing me the way also i'v been like this since last week reason i didn't ask in the first place is because i thought it was already answered already and i searched but couldn't find the right answer
but thanks to a guru like you i fixed it .
Edit - testing phone , seems to be doing something at the g1 screen.
Edit 2 - i think it might be ... bricked , hold on.
Edit 3 - got it into recovery lets see from here.
**** it tomorrow i get a new phone anyways time to put this demon to sleep
ok i am not going anywhere can't get lift off .
i have amonra recovery in a zip file if you can flash it via fastboot?
I can try that but if i can get into fast boot (is it the little balltracker thingy and the power button? if so i think my fastboot is broken because it just shows a blue light with no signal of the screen on )
What i have try'ed is that wipe script ohsaka-super-wipe <- and i am trying to get SenseLX v3.1 to run but all my attempts just lead me back to the recovery screen for some weird reason
also don't know if this info will help at all but i got a 16gb sdcard and getting another one soon just hope it's better class
Hold on let me see something
also i flashed my hboot alot of times so maybe it's something with that.
well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 & 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899
ldrifta said:
well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 &1. 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899
Click to expand...
Click to collapse
yep i have it, also following guide gonna report back in a few minutes
Edit - i got both hboot0013d-signed.zip and radio-2_22_27_08-signed.zip in my sdcard meaning i might have flashed them already so i don't see why it should be taking me to recovery
edit 2 bad hboot / E:missing bitmap Progress_empty/fill code -1 2x didn't wanna risk the real brick so i didn't install it.
Edit 3 E: - blah blah blah failure at line 3
well its' back to the drawing board for me..
and well fastboot don't work (camera button + power button don't do anything)
Now would'ya look at that it started working to an htc screen doing something alright
it hates me i swear.
lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?
ldrifta said:
lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?
Click to expand...
Click to collapse
Fuucucuc my luck was supposed to get a new phone today
also
NO i can't find out what radio/spl i have i can flash but it will give me a E:/hboot error
well you find out by powering on device in hboot mode, holding camera+power or even try back+power
Dream100 PVT 32b
HSPL.10.95.3000
CPLD - 4
Radio -2.22.28.25
thank you for the info since the camera button was be stubborn
i see i didn't have hboot maybe that's why it's was giving me errors'
----
got it back to default
-----
goddam my luck sucks almost had another one in the hook today (samsung captivate)

[Q] Factory reset not working

Hi friends,
I really hope somebody can help me out here..
My mum's Moto G 2014 (stock rom, just like it came out of the box, no tinkering, nothing) started acting weird. It had force-closes all over, nothing worked. So I boot into fastboot mode, select "Factory". The factory reset doesn't work - user data is clearly still there when I boot.
So I try wiping user data and cache with fastboot from the PC (linux). Command runs through, no error message. But the user data is still there when I boot - I still get 100 force-closes, the thing is unusable.
Next I go ahead and unlock the bootloader (which should wipe all data, right)? Again, userdata is still there when I boot.
Then I flash TWRP. But when I boot into fastboot and select "recovery", the screen just goes dark. Same after I flash CWM instead. (And the same, incidentally, as it was with stock recovery - selecting "recovery" just makes the screen go dark).
I am left clueless ... having voided the warranty by unlocking the bootloader. Any pointers?
Thanks, guys.
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Tel864 said:
Power off your phone. When the screen goes black, press and hold the Volume Down button with one finger. Then, while still holding this button, press and hold the Power button with another finger. This will bring up the Bootloader menu, then tap the Volume Down button once to highlight Recovery Mode. From here, simply press the Volume up once, and TWRP recovery should come right up. Touch Wipe and you'll see the Factory Reset.
Click to expand...
Click to collapse
But I think as he said, he can't enter the recovery mode.
Did you try to flash a stock rom?
You're right, I missed that part about going dark when choosing recovery.
Lars124 said:
Did you try to flash a stock rom?
Click to expand...
Click to collapse
No - not yet. Where would I get the stock ROMs? I think I've got the XT1068 version of the phone, (Germany, dual-SIM).
Can I just flash the ROM with fastboot from the PC? Without having a custom recovery on the device? (as I said, flashing TWRP or CWM with fastboot didn't work, no error message but no success either).
EDIT: I now managed to get into the stock recovery - I just didn't know I had to press the Vol-Up-Key to confirm (and when the android on its back shows, then hold Power for a few seconds and tap Vol UP to enter the recovery). So I'm in the recovery now. However, selecting "wipe data / factory reset" still doesn't work. I get these error messages:
{
"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"
}
Doesn't look good, does it?
Thanks so much!
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
dazeone said:
What commands did you enter when in download mode on the phone? What commands on the pc did you enter and what did your phone say in download mode while doing it?
Click to expand...
Click to collapse
First I entered
Code:
fastboot erase cache
The PC said:
Code:
erasing 'cache'...
OKAY [ 0.033s]
finished.
The phone said:
Code:
cmd:getvar:partition-type:cache
cmd: erase:cache
Then I hit
Code:
fastboot erase userdata
The PC said:
Code:
erasing 'userdata'...
OKAY [ 0.034s]
finished.
And the phone said:
Code:
cmd:getvar:partition-type:userdata
cmd: erase:userdata
So no error message there (unlike when I start a wipe/reset from the stock recovery). The userdata aren't erased in either case - all the apps are still there (and I'm bombarded with force-closes of all sorts of apps and services every 0.5 seconds)
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
Thanks! I'll definitely try that. But I don't dare get my hopes up after flashing CWM and TWRP didn't work (and factory reset neither). This really starts looking like a brick to me.
That's really strange.
Flash the stock rom and we will see what happens.
Lars124 said:
Yes, you flash your stock rom via fastboot and you don't need a custom recovery.
Check this thread and look for your version:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I think you can take this one:
https://drive.google.com/file/d/0B_OYdZXdfmnbY092bUIxaTkxRjg/view
Click to expand...
Click to collapse
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
loxdp said:
I downloaded and flashed all parts of the ROM in the order suggested in the .bat file. It turned out as I suspected: No error message (neither in fastboot on the PC nor on the device while flashing), but no change on the device. Even after flashing the stock ROM and erasing userdata and cache at the end of the process, my old apps are still there and nothing appears to have changed. Still getting a ton of force-closes, it's unusable.
It's as if the phone is in read-only mode, I erasing userdata or flashing new ROM doesn't do anything. The only thing I have to go on at this point are the error messages I posted in the photo above (after trying to wipe from the stock recovery:
Code:
Formatting /data
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed[/B]
Formatting /cache
[B]E:
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed[/B]
Click to expand...
Click to collapse
This. I am also having exactly this problem (of endless force quits and inability to flash stock), with precisely the same error message when resetting from recovery. The thread I started '[Q] Custom Recovery Only Works By "fastboot boot"' turns out to have been the wrong title...it seems likely the reason I can't flash a custom recovery (despite unlocked bootloader) is the same reason I can't format partitions either (stock recovery can't, nor can TWRP format /data). Although adb shell can be used for manually formatting partitions, it is serious stuff not to be attempted casually ("instant expert" disease is a leading cause of death so I have not tried it.
Sadly, I can't offer you any help other than to add to link our threads in the hope that something I've discovered may lead a knowledgeable dev to the source of this problem.
Same problem here.
Any write operation fails, while fastboot claims anything was "OKAY".
Only "fastboot -w" gives some hint to the actual problem:
Code:
# fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.077s]
erasing 'cache'...
OKAY [ 0.014s]
finished. total time: 0.091s
However, I was not able to solve it.
I suspect this to be a hardware failure but I did not give up hope completely yet :-\
I have the exact same problem
Has anyone solved it yet?
bump
Thats seems to be my problem too.
With stock recovery and stock rom I didn't manage to wipe cache and user data. I also try it with fastboot but nothing. Nothing clear no erase at all.
Desparate and waiting a solution
Same problem - can't erase, can't flash.
Should ask help from Motorola Support.
Will call to their support and hope they will provide me 2nd level assist, not just advice to use warranty. No official Motorola in my country.
For anyone who would try to get support - chat on site is useless - they will tell you to do Wipe in recovery.
For additional support - call (US) Motorola Support 1-800-734-5870 and try to reach advanced support.
*Motorola chat support advised me to use Talkatone app to make a call, since I'm out of US.
**Get all of available phone docs - IMEI and other stuff.
I can't try their support since MotoG2 is of my girlfriends and is away now.
Support told me to call back only when I will hold the phone in my hands and will have IMEI to provide.
RSD Lite 6.2.4 works with Moto G, earlier versions would not work.
Same stuff - flashed ok but nothing changes.
If we use "mfastboot boot boot.img"
Device shows "updating android applications 1 of 7", then "Starting Android", but then black screen. Again.
But better than was - just black screen without any signs.
Is there any way to boot up different bootloader to get it's fastboot?
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Poeta said:
Anyone have tried to lock the bootloader, reflash the stock rom from fastboot and unlock again the bootloader?
A similar situation happened to me and this resolve the problem.
Click to expand...
Click to collapse
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Darksl1der said:
When locking bootloader - reboot is required since no commands will work.
But after rebooting everything is still same. Bootloader still UNlocked.
Guys, what you think about this?
http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html
about partition images
Aaand this
http://android.stackexchange.com/questions/58027/updater-script-for-flashing-raw-partition-image
about dd flashing raw
Click to expand...
Click to collapse
It seems to be a motherboard problem... Warranty.

[GUIDE] Unbrick your device or recover from bootloop

Assalamu alaikum people,
Those on the telegram group know that I bugged you a lot about needing data partition. Because of my experience with unbricking and recovering the device, I can tell you a sureshot method that works to restore the device. Do not use this method if your device already works. There seems to be a lot of files inside the data partition which are necessary for the stock ROM to work. This method asks you to wipe data partition and so system update will not work. This should be a last resort. .
Many people seem to have come to the situation where they are in fastboot, and it says frp locked, so they cannot flash new twrp. And the system seems to be in bootloop and it does not work. What to do from there?
1. Download this file ->https://www.androidfilehost.com/?fid=673956719939832337.
2. In your SDCard, create a folder called TWRP and inside it, create a folder called BACKUPS (all in capitals). Inside this, create a folder called 7xtwrpbackup (small letters) and paste the contents of the zip that you have downloaded into this.
3. Boot to twrp in your device and go to restore. There you should see a folder 7xtwrpbackup. If you select it, you will get a checkbox below with recovery_ramdisk like 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"
}
4. Select Yes and after restore complete, go back and select reboot and reboot to recovery.
5. Now, the new twrp will boot. In the new twrp, I want you to first go to wipe -> advanced wipe -> select dalvik/art cache, cache, data, internal storage and system.
6. Come back once again and select wipe, and this time, select format data. It will ask you to type yes. After that is done, come back once again.
7. Now select install and in that, install the openkirin RR image from telegram group or here -> https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 (This step is optional because openkirin RR has a greater chance of booting than stock ROM. You can skip this step and directly boot stock)
8. Your system must boot now. If it boots, then all partitions are good. You can boot stock.
9. You can now can download stock from my post here and repeat from step 5-> https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
If this does not work, then look at the second method in the next post
Second method
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Bricked my device Twrp doesn't work
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Oushal kDee said:
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Click to expand...
Click to collapse
Download vendor partition from here https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
Hello i am siddharth, i have relocked my oem by fastboot oem relock -------- after that yes/no option came i click on yes. It starts factory formatting after completion of formatting when the phone starts its showing your device has failed verification and got stuck in it. When i press reboot option it will directly comes to erecovery mode wher the option came to download new recovery when i connect my phone with wifi it starts searching for some time after that system update failed.
When i starts mobile directly to fastboot mode by pressing volume down button and power button the white screen with android comes appear i.e fastboot mode screen. In that screen in green colour i found that
Phone Relock
FRP lock
When ever i m trying to find the device in fastboot mode by typing fastboot devices my device showing there but no other command is working such as fastboot oem unlock -------, fastboot flash system system.img, all the time it comes Failed.
I have downloaded many UPDATE.APP and tried to load that by dload method but every time after 5% it come Failed to install.
I have downloaded UPDATE.APP form ur given link also. This is only the image in which my phone comes upto 23% install after dat failed.
Nothing working for me. Kindly help me.
Mail me if there is any solution @
[email protected]
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
None of the method worked for me my device still bootloops no matter what system.img or rom zip file i flash. The emui recovery method didn't work for me as it loaded up to 5% and then failed instantly. Please help me unbrick my 9 lite bro. Could you provide me the boot.img? i think my phone got bricked because i tried to i install magisk on treble rom (i guess?). But anyway PLEASE HELP ME (
Try extracting kernel.img from an update and flash that. It fixed it for me.
hi twrp is bootlooping as well
cant access
---------- Post added at 07:15 PM ---------- Previous post was at 06:52 PM ----------
hey i used the twrp from the link made a backup restored it now a get bootloop cant get into twrp it goes in ti it then it fcs then am back to bootloader unlocked warning
hi anyone got custom.img and userdata.img from this LLDL31C432B130 800130 a need to restore my device
Same Problem
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem, if anyone has solution plz help.
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem.
mine goes to 5% doesnt do anything and then it fails
aveemashfaq said:
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Click to expand...
Click to collapse
But this is for L31
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
My phone's frp and bootloader locked,and phone is booting to erecovery,what to do
need help with LLD-AL10C675 indian version
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
sunny_deed said:
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
Click to expand...
Click to collapse
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
BS4388 said:
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
Click to expand...
Click to collapse
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
sunny_deed said:
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
Click to expand...
Click to collapse
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Sparkrite said:
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Click to expand...
Click to collapse
there is no Fullota version in there
sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
Go:
https://forum.xda-developers.com/9-lite/development/stock-rom-indian-firmware-c675-t3813875
sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
My bad, I was only trying to help.............
Anyway you have it now (post above) thanks to @BS4388 and @VigneshS007 .

Question Oneplus 10 Pro stuck in Bootloop

So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
{
"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"
}
biglo said:
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
View attachment 5694575
Click to expand...
Click to collapse
Are you rooted? Can you get in recovery? What model number?
twinnfamous said:
Are you rooted? Can you get in recovery? What model number?
Click to expand...
Click to collapse
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
biglo said:
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
Click to expand...
Click to collapse
Have you tried flashing stock boot.img or factory resetting?
twinnfamous said:
Have you tried flashing stock boot.img or factory resetting?
Click to expand...
Click to collapse
Yes, I tried both options without success.
biglo said:
Yes, I tried both options without success.
Click to expand...
Click to collapse
That's not good usually one or the other fixes it. Only thing I can think of is flashing all images in fastboot. But try vendor_boot first
When this happened to me on my OP6 when I had it and when I couldn't recover it with MSM tools or boot.img, I decided it is motherboard failure.
But I would try fastboot ROM if I were you. If it doesn't help, I will send it to the service center.
You may have booted a patched yet not made it permanent so when you rebooted you lost it.
If that rings a bell then just boot a patched boot image. Not flash.. once you're booted and in the system just open magisk and click direct install..
Reboot and it should be permanent.
Beyond that you can go to recovery or fastboot to get back in business although you'll lose your data
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
unsafe8989 said:
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
Click to expand...
Click to collapse
I tried switching slots the other day, it gave me the same results.
hello did you found any solutions?
biglo said:
I tried switching slots the other day, it gave me the same results.
Click to expand...
Click to collapse
That means you have no boot img on it
try to flash a boot img to slot a and slot b
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
dladz said:
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
Click to expand...
Click to collapse
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
*-MaCK-* said:
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
Click to expand...
Click to collapse
Doesn't help that the forums went through a crap update that broke the sections.
That being said, you're looking for a guide so that's your key word.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
There's a good few of them, the screen shot is taken from the main OnePlus 10 pro forum section, I can see two. Mine and the 2215 one.
Also when you say 'installed' I hope you meant boot and not flash, booting is risk free.. Read my thread and it'll make sense.
I wish people would read more...cause it all here...just need to take the time and read alot of post...to find what they are looking for...lol

Categories

Resources