Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
lucent6408d said:
Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
Click to expand...
Click to collapse
Just flash the system.img with fastboot.
https://dl.google.com/dl/android/aosp/volantis-lrx22c-factory-8d83cd9b.tgz
They changed the way updating happens. If your rooted never plan on getting an OTA again
AlEsC said:
Just flash the system.img with fastboot.
https://dl.google.com/dl/android/aosp/volantis-lrx22c-factory-8d83cd9b.tgz
Click to expand...
Click to collapse
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
lucent6408d said:
Good morning Guy,
i have a simple question that for me is not so simple because clearly i need some help. I have unlocked & rooted my tablet however now I get a notification for the Lollipop 5.0.1 OTA but when I try to install it and it reboots it then goes into the TRWP recovery mode and nothing else and if i choose to reboot from there the it reboots fine but without the upgrade. Any idea on how to fix this issue?
Click to expand...
Click to collapse
Is possible that the problem is because you have a Custom Recovery (TRWP) installed.
Try to flash the Recovery Stock, and then maybe OTA can be installed. If not, try to flash whole Factory Image.
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
You will have to extract several times to find the .img files
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
Use winrar or 7-zip to extract it. Inside is a zip file, extract that too. There you will find the system.img
Sent from my Nexus 9 using XDA Free mobile app
lucent6408d said:
Hi,
this link does not take me to the .img file. this is a .tgz and if i extract I get a .tar. my apologies for my ignorance lol
Click to expand...
Click to collapse
The you must extract .tar again. The you must use .bat or extract a .ZIP and then:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase cache
fastboot erase vendor
fastboot erase userdata
pause
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
But with this, all your data will be erased.
lept_2014 said:
The you must extract .tar again. The you must use .bat or extract a .ZIP and then:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase cache
fastboot erase vendor
fastboot erase userdata
pause
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
But with this, all your data will be erased.
Click to expand...
Click to collapse
You don't have to erase everything to update.
Code:
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
Will update your tablet without wiping everything.
Related
I used to have one but I lost it and I don't know if you have tried but its really hard to find one.
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
bunchies said:
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
Click to expand...
Click to collapse
Well basically I need the txt file in the boot img. my phone is s-on and I always have to flash the ph
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Or just "fastboot boot recovery.zip" and flash normally, if you are S-ON and BOOT recovery via fastboot, you can flash the ROM normally and not have to manually flash the boot.img in Fastboot like you do if you flash the ROM from an installed recovery.
bunchies said:
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Click to expand...
Click to collapse
As a mac user I tried this. With adb all set up on the mac to use terminal (the whole folder and everything was set up long ago when unlocking). I have to use the command ./fastboot instead of just fastboot with terminal. Anyway, when ./fastboot flash boot boot.img it never works. It seems like it works, but then the phone just goes into the white HTC screen and is stuck there. It never boots.
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
noRetail said:
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
Click to expand...
Click to collapse
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Adarsh1998 said:
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Click to expand...
Click to collapse
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
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
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
noRetail said:
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
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
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Adarsh1998 said:
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Click to expand...
Click to collapse
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
noRetail said:
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
Click to expand...
Click to collapse
All i tried no use
Adarsh1998 said:
All i tried no use
Click to expand...
Click to collapse
this is bad, I try to go back to stock 4.4.4 to clean the phone and if everything is ok would install the cm11 again, I see no other solution, sorry not help much.
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
Try wipe partition system, this may work
GabrielRW said:
Try wipe partition system, this may work
Click to expand...
Click to collapse
How in twrp?
flash kernel again
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Adarsh1998 said:
How in twrp?
Click to expand...
Click to collapse
Yes, go to advanced wipe, make a full wipe except sdcard and flash again the ROM. Sorry for my bad english
kushal.purkar said:
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Click to expand...
Click to collapse
How to pl, help
Where is link?
this may help
Adarsh1998 said:
How to pl, help
Where is link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
Any body can help me how to repack update.app (stock rom) into flashable Zip
My phone have unlocked bootloader and have twrp.
Impossible to flash stockroom with update.app file via twrp.
I`ve tired using custom rom so many bug.
I want rolling back into stockrom with keep twrp n unlocked bootloader.
I've lost my backup
Sorry bad English
Device SCL-L21
1. extract boot.img and system.img for update.app using huawei update extractor
2. copy them into fastboot folder on your computer
3. go into fastboot mode and type this on you computer:
fastboot flash boot boot.img
&
fastboot flash system system.img
3. when completed just type "fastboot reboot"
4. wipe data and cache in recovery to start your phone like new
that`s what i do when i flash stock rom
TheWarrior12345 said:
1. extract boot.img and system.img for update.app using huawei update extractor
2. copy them into fastboot folder on your computer
3. go into fastboot mode and type this on you computer:
fastboot flash boot boot.img
&
fastboot flash system system.img
3. when completed just type "fastboot reboot"
4. wipe data and cache in recovery to start your phone like new
that`s what i do when i flash stock rom
Click to expand...
Click to collapse
Hi man, itś so many years dead discussion, but now i need upgrade my Honor 5C. I don´t know if i´ve make something bad, but if i try flash system from stock rom (NEM-L21C432B364), my phone is dead. Only recovery and fastboot mode is working. I´ve try upgrade from version B132. Can you help me please? Now I am not sure, if upgrade version B132 directly to B364 is OK....
So i changed back to stock rom and everything is working fine except the part where i cant get any mobile signal.
Here´s what i did:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
When flashing cust it gave an error, maybe thats it?
Thanks!
henryke9 said:
So i changed back to stock rom and everything is working fine except the part where i cant get any mobile signal.
Here´s what i did:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
When flashing cust it gave an error, maybe thats it?
Thanks!
Click to expand...
Click to collapse
Did you flash right firmware according to your model and build number??