Related
after i got my tf700 tablet i unlocked the bootloader and put cwm and cm11 on it, without any problems.
then i tried the same thing on my brothers tf300 i accidentally bricked it, after we bought another one i used the nvflash bricksafe setup on my tf700 so the same thing would not happen to me. then i changed from cwm to philz. later i tried to change the wallpaper in philz and my device froze, so i rebooted and found myself bricked. so i used apx to recover. i got android functionality back but now i have some issues.
1. i cant access recovery, selecting the rck command results in an error: unrecoverable bootloader error (0x00000000)
2. i cant make fastboot flash commands work to reflash a recovery, because the tablet freezes after i hit enter
i have used the "fastboot erase recovery" command too, which seemed to work...
recovery mode usability needs to be restored and possibly a fresh install of the bootloader too.
any help putting it back together either through apx recovery or the android system would be much appriciated!
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
berndblb said:
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Buster99 said:
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
thanks for the instructions but i think i will leave this as a last resort as i would rather not have to redo everything i have already done to my device, i hate starting over
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
berndblb said:
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
kirbyonwarpstar said:
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
Click to expand...
Click to collapse
In that case, it's easy:
Flash system blob
Flash custom recovery
Restore nandroid
Sent from my K00C using Tapatalk
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Megadarkwood said:
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Click to expand...
Click to collapse
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
http://waynekent.com/page6.html
NWKENT said:
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
Click to expand...
Click to collapse
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Megadarkwood said:
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Click to expand...
Click to collapse
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >> http://sbf.droid-developers.org/phone.php?device=14
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >>
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Megadarkwood said:
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Click to expand...
Click to collapse
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #
Click to expand...
Click to collapse
I am not concerned about any data, just need to get it working. I will flash TWRP as soon as I get back to my computer
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
nArdow said:
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, how am I supposed to sideload the .img for TWRP?
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Won't work, says "Waiting for Device"
Megadarkwood said:
Won't work, says "Waiting for Device"
Click to expand...
Click to collapse
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
The Closet Candian said:
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
Click to expand...
Click to collapse
Alright, but do I need a OS file or something in the folder before I do this?
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Megadarkwood said:
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Click to expand...
Click to collapse
Since you are in fastboot mode you should use "fastboot devices".
meekrawb said:
Since you are in fastboot mode you should use "fastboot devices".
Click to expand...
Click to collapse
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
Only thing I can think of is to re-install the drivers or try different USB ports.
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
eg0097 said:
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
Click to expand...
Click to collapse
Got TWRP on and everything flashed but carbon is still in a boot loop.
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yeah I hear the beep.
FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?
Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg
android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.
bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??
So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.
Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!
No one? :/
Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that
You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=295200
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
What does branded devices mean?
What about locking the bootloader. I noticed recovery image is not included
Recovery is a part of the boot image for A/B devices such as Oneplus 7.
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
arvindgr said:
What does branded devices mean?
Click to expand...
Click to collapse
Branded device means it is customized by mobile service provider, such as T Mobile.
any way to flash this without erasing data
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
Just remove -w from the script
arvindgr said:
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Click to expand...
Click to collapse
Just flash the GM57AA rom, there are boths in the link you can find in the first post
Ismael034 said:
What about locking the bootloader. I noticed recovery image is not included
Click to expand...
Click to collapse
Hello, I have sent you a message regarding this message. a greeting.
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
fusk said:
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
Click to expand...
Click to collapse
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
mauronofrio said:
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
Click to expand...
Click to collapse
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
fusk said:
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
Click to expand...
Click to collapse
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
fusk said:
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
Click to expand...
Click to collapse
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
Click to expand...
Click to collapse
@mauronofrio Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
Click to expand...
Click to collapse
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
fusk said:
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
Click to expand...
Click to collapse
Thank you for answering friend, what version do you have of OnePlus 7? Do you have the Chinese version Gm1900 ?.
Before putting the rom by fastboot did you have Twrp installed?
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
Click to expand...
Click to collapse
Yes it will work on the oneplus 7, there are 2 different thread for the fastboot roms this one is for oneplus 7 only. AA or BA there are not a lot of.differences, just use the one you prefer.
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
cakriez92 said:
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
Click to expand...
Click to collapse
Yes