So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.
It Doesn't work only say failed xD
Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?
tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps
Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?
tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.
Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?
and do i need a cutom rom with 4.4.4????????
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps
Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.
It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp
I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan
not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
i think this fix doesn't work because i can only sideload my roms and gapps xD
Related
Hi, hope I'm not dubbel posting... but here is my PROBLEM:
I have the now-well-known problem (hardware?) when the phone (i9020) fails to mount the sdcard and also refuses to boot.
E:failed to mount /sdcard (No such file or directory)
This problem occured now and then until it now became permanent. The last thing I did while the sd-card still was accessible was to unroot the phone. (su-XXXX-signed.zip on the sd-card)
I'm pretty sure the process of rooting finished but the phone then decided not to boot any more. (E:failed to mount /sdcard etc...) - Perfect timing...
I have not been able to verify this since the booting now stops at the Google-text.
I can connect to the phone with SDK Manager and the bootloader is still unlocked. I can also fastboot it with recovery-clockwork-5.0.2.0-crespo.img.
I also still have stock rom.
What I would like to do is to unroot and lock the boot manager before I send my unit to Samsung.
Locking the boot manager shouldn't be a problem but how do I unroot?
I can't flash by putting .zip with stock rom on sdcard because the sdcard can't be mounted...
Can I flash it with stock rom via fastboot...?
...or are there any other methods to unroot it...?
Is there by any chance a way to check if the phone actually is rooted?
Thanks in advance.
Flash stock recovery, lock bootloader and send it in for warranty, because it can't boot or mount anything then they won't be able to tell
Sent from my ice cream powered Nexus S
DarkhShadow said:
Flash stock recovery, lock bootloader and send it in for warranty, because it can't boot or mount anything then they won't be able to tell
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Might be that simple...
But it's the flashing of stock recovery I can't do. Question is if they are able to see that it is rooted?
Locking the bootloader shouldn't be a problem since I can use fastboot.
It's just the rooting that concerns me...
jbr64 said:
Might be that simple...
But it's the flashing of stock recovery I can't do. Question is if they are able to see that it is rooted?
Locking the bootloader shouldn't be a problem since I can use fastboot.
It's just the rooting that concerns me...
Click to expand...
Click to collapse
Your phone can't boot because the hardware has failed, they cant tell if you have a custom rom let alone root
Sent from my ice cream powered Nexus S
DarkhShadow said:
Your phone can't boot because the hardware has failed, they cant tell if you have a custom rom let alone root
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Makes sense...you're probably right. I guess I'll just lock the bootloader and ship the phone.
Thanks!
But cant you flash stock recovery via fastboot? 'Fastboot flash recovery (what ever you called it).img'
sent while eating an ice cream sandwich in the matr1x
I flash roms therefore i am!
4I-I said:
But cant you flash stock recovery via fastboot? 'Fastboot flash recovery (what ever you called it).img'
sent while eating an ice cream sandwich in the matr1x
I flash roms therefore i am!
Click to expand...
Click to collapse
Leave the boot loader unlocked when you do this. Then lock it.
Sent from my Nexus S using Tapatalk
4I-I said:
But cant you flash stock recovery via fastboot? 'Fastboot flash recovery (what ever you called it).img'
sent while eating an ice cream sandwich in the matr1x
I flash roms therefore i am!
Click to expand...
Click to collapse
Yes, that is what I would like to do but the only stock rom I have is the .zip from this thread:
http://forum.xda-developers.com/showthread.php?t=1445570
I don't know how to flash it with fastboot.
'Fastboot update' doesn't work and I don't know the correct syntax for 'fastboot flash'
jbr64 said:
Yes, that is what I would like to do but the only stock rom I have is the .zip from this thread:
http://forum.xda-developers.com/showthread.php?t=1445570
I don't know how to flash it with fastboot.
'Fastboot update' doesn't work and I don't know the correct syntax for 'fastboot flash'
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecovery.img
Sent from my ice cream powered Nexus S
DarkhShadow said:
Fastboot flash recovery nameofrecovery.img
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Okay, thanks.
Mabye getting somewhat closer...
The process stops with a writing failure.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery ZD3PyN0t.zip
sending 'recovery' (164624 KB)...
OKAY [ 20.735s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 20.745s
and the phone displays:
Exceed blocks 0x00000284 > 0x0000001c
Looks like it's not too happy with a certain memory area...?
Could it be a problem with the unpacking of the .zip file ?
Sounds a little far fetched perhaps...?
jbr64 said:
Okay, thanks.
Mabye getting somewhat closer...
The process stops with a writing failure.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery ZD3PyN0t.zip
sending 'recovery' (164624 KB)...
OKAY [ 20.735s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 20.745s
and the phone displays:
Exceed blocks 0x00000284 > 0x0000001c
Looks like it's not too happy with a certain memory area...?
Could it be a problem with the unpacking of the .zip file ?
Sounds a little far fetched perhaps...?
Click to expand...
Click to collapse
Your trying to flash a .zip, you don't do that, try searching forums for a stock recovery .img, I'm pretty sire there's one around
Sent from my ice cream powered Nexus S
http://forum.xda-developers.com/showthread.php?t=1078213
Read this
Eat at Joe's
t1n0m3n said:
http://forum.xda-developers.com/showthread.php?t=1078213
Read this
Eat at Joe's
Click to expand...
Click to collapse
Thank's.
I have an european I9020 version and that post referes to NS4G as I interpret it...?
I'll keep searching though.
That link, while not for your model, does contain the commands that you need to use fast boot.
I will break it down for you:
Unzip that zip file you have into your ADB (fastboot) directory.
Run these commands at a command prompt in the ADB directory:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Reboot your device.
Return your device.
Discalaimer: You may need to adjust the names of the .img files depending on the file names inside your stock rom zip.
t1n0m3n said:
That link, while not for your model, does contain the commands that you need to use fast boot.
I will break it down for you:
Unzip that zip file you have into your ADB (fastboot) directory.
Run these commands at a command prompt in the ADB directory:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Reboot your device.
Return your device.
Discalaimer: You may need to adjust the names of the .img files depending on the file names inside your stock rom zip.
Click to expand...
Click to collapse
I knew that...
Thank you - now I get it.
Just one more obstacle then... the stock rom contains only boot.img, bootloader.img and radio.img.
In addition to those three .img-files it also contains three folders:
'META-INF', 'recovery' and 'system'.
I guess I nedd the other .img-files as well...??
Yea you need stock system image(.img). Google should have them on the android dev site.
Sent from my Nexus S 4G
same
jbr64 said:
Hi, hope I'm not dubbel posting... but here is my PROBLEM:
I have the now-well-known problem (hardware?) when the phone (i9020) fails to mount the sdcard and also refuses to boot.
E:failed to mount /sdcard (No such file or directory)
This problem occured now and then until it now became permanent. The last thing I did while the sd-card still was accessible was to unroot the phone. (su-XXXX-signed.zip on the sd-card)
I'm pretty sure the process of rooting finished but the phone then decided not to boot any more. (E:failed to mount /sdcard etc...) - Perfect timing...
I have not been able to verify this since the booting now stops at the Google-text.
I can connect to the phone with SDK Manager and the bootloader is still unlocked. I can also fastboot it with recovery-clockwork-5.0.2.0-crespo.img.
What I would like to do is to unroot and lock the boot manager before I send my unit to Samsung.
Locking the boot manager shouldn't be a problem but how do I unroot?
I can't flash by putting .zip with stock rom on sdcard because the sdcard can't be mounted...
Can I flash it with stock rom via fastboot...?
...or are there any other methods to unroot it...?
Is there by any chance a way to check if the phone actually is rooted?
Thanks in advance.
Click to expand...
Click to collapse
this is also a problem for me but i can mount my sd card
i dont know what to do and im not sure how to unroot a non bootable device because i cant plug my tablet into my computer. im new to android so i just rooted my device with no costome roms and no CWM just rooted. i installed the chainfire files incorrectly and my tablet stopped booting. as my tablet does not supply and power to the usb drive when turned off i can use my sd card and im am quite confident that they will notice its rooted and wont replace it
if anyone can help plz do
thanks in advance
Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?
Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.
I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.
What about formatting system partition via cwm? Failed too?
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.
_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.
It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?
Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.
Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?
ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
AndySOS said:
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
Click to expand...
Click to collapse
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
jollywhitefoot said:
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
Click to expand...
Click to collapse
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
AndySOS said:
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
Click to expand...
Click to collapse
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
jollywhitefoot said:
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
Click to expand...
Click to collapse
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
AndySOS said:
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
Click to expand...
Click to collapse
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
jollywhitefoot said:
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
Click to expand...
Click to collapse
It says that." fastboot is not working proprely" . And yes it does show my device.
AndySOS said:
It says that." fastboot is not working proprely" . And yes it does show my device.
Click to expand...
Click to collapse
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
jollywhitefoot said:
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
Click to expand...
Click to collapse
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
AndySOS said:
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
Click to expand...
Click to collapse
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
jollywhitefoot said:
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
Click to expand...
Click to collapse
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
AndySOS said:
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
Click to expand...
Click to collapse
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
jollywhitefoot said:
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
Click to expand...
Click to collapse
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
AndySOS said:
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
Click to expand...
Click to collapse
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
jollywhitefoot said:
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
Click to expand...
Click to collapse
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
AndySOS said:
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
Click to expand...
Click to collapse
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
jollywhitefoot said:
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
Click to expand...
Click to collapse
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
AndySOS said:
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
Click to expand...
Click to collapse
ok. cool. no problem. glad you got it working.
Well, I was messing around in TWRP without really knowing what I was doing, and selected all boxes in the Wipe section. Now, when I try to install the stock rom, I get an error telling me that gpt.bin can't be downgraded, and when I try to sideload a rom via TWRP, I get another error saying that the .zip file is invalid. Can't send pictures of anything on the phone since it is the only one I have. Sorry.
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
ctcsilva said:
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
Click to expand...
Click to collapse
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Amar 721 said:
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Click to expand...
Click to collapse
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
ctcsilva said:
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
Click to expand...
Click to collapse
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Amar 721 said:
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Click to expand...
Click to collapse
Yes, I do. Just tried right now.
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem lock begin
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.104s]
finished. total time: 0.105s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash partition zip/gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.168s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
@ctcsilva : Flash TWRP
Code:
fastboot flash recovery twrp.img
where twrp.img is the name of twrp file. Now boot into TWRP, go to Mount and check that /data is selected, if not, then mark it and select back.
Now go to Wipe>Advanced Wipe. Select data and tap Repair or Change File System. Now select Repair File system and swipe to confirm. Now go to Wipe> Factory Reset and swipe to confirm. Then Reboot>bootloader.
Connect the phone to pc and flash stock recovery
Code:
fastboot flash recovery recovery.img
, and boot into it. Press and hold power and press volume up key once, you should see the options now. Select factory reset and confirm. Now reflash the stock firmware from fastboot and see if it boots.
Edit :- Use this guide, do not attempt to relock bootloader, it won't lock unless every file is flashed, which is again impossible because the firmware is older than the one present in the phone.
Broadcasted from Zeta Reticuli
ctcsilva said:
Yes, I do. Just tried right now.
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
Click to expand...
Click to collapse
oem is not unlocked : ( you should try asking help from a senior member like ishubhamsingh or other i guess they can definetly help you