hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
Related
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
wisdomlight said:
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
Click to expand...
Click to collapse
normally I just do
Code:
fastboot flash recovery <recovery-image-file>
Also how do you attempt to boot recovery?
- VolDn+Pwr ?
- adb reboot recovery ?
What if you flash stock recovery or twrp?
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
wisdomlight said:
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
Click to expand...
Click to collapse
if you unpack cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip from cyngn.com you may try to flash stock COS 13.0 as follows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue
Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause
Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.
If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.
Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.
Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.
same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.
Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.
philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?
I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.