i've got the x510 with 2gb of ram version. it came with the latest October update presintalled build 20151012. till now checking for update doesn't reflect the Marshmallow update.
recovery is not working (even by adb it goes to an android pic with no text or No Command available)
tried flashing recovery, no luck, reflashed all the available stock roms on the forum with no luck neither, no recovery and no marshmallow update
all flashing was done through SP Flash, with format or download only, no difference. stock original cable was used, vcom drivers present and SP tool read the phone perfectly.
X510-D5110-Androidone-20150824, X510-D5110-Androidone-20151012, X510-A1-FIX-20150824.
i even tried flashing twrp and pushing the Marshmallow update through it which never succeeded
any idea ? hint ? help item that i can do ?
yacbos said:
i've got the x510 with 2gb of ram version. it came with the latest October update presintalled build 20151012. till now checking for update doesn't reflect the Marshmallow update.
recovery is not working (even by adb it goes to an android pic with no text or No Command available)
tried flashing recovery, no luck, reflashed all the available stock roms on the forum with no luck neither, no recovery and no marshmallow update
all flashing was done through SP Flash, with format or download only, no difference. stock original cable was used, vcom drivers present and SP tool read the phone perfectly.
X510-D5110-Androidone-20150824, X510-D5110-Androidone-20151012, X510-A1-FIX-20150824.
i even tried flashing twrp and pushing the Marshmallow update through it which never succeeded
any idea ? hint ? help item that i can do ?
Click to expand...
Click to collapse
You must be in 2015 December 5.1.1 update to Install Marshmallow. 20150824 or 20151012 will NOT support directly install MM.
So update to 2015 December update. If you cant find through OTA, just manually download the OTA from forum (search somewhere).
to access recovery : go to adb and reboot to recovery. U will see the Android Logo without any text. Here press the Power and Volume+ button for 5 seconds and leave the keys. u will see the recovery menu.
2.1
http://www.techspot.com/drivers/downloadnow/17759/?evp=5baf2d8ad10473e98819c64b892e87e5&file=1
2.1 PRO
http://www.techspot.com/drivers/downloadnow/17759/?evp=5baf2d8ad10473e98819c64b892e87e5&file=2
Backup in my MEGA
im on 3.0.0 right now. can i downgrade to 2.1? can you show me how? tried out but stuck at nvidia boot screen
you can downgrade, but right after you start up it'll auto-upgrade to 3.0 again so pretty pointless.
Mistake
slim94 said:
you can downgrade, but right after you start up it'll auto-upgrade to 3.0 again so pretty pointless.
Click to expand...
Click to collapse
what if i flash the 2.1 firmware, flash twrp right after and restore a backup from 2.1 with data, so that it doesnt force the update?
Hi, the links points to 3.1 firmware.
Here are the 2.1 Links
http://drivers.softpedia.com/downloadTag/SHIELD+Android+TV+Firmware+2.1
This is useful for remix os on shield TV.
Is this for installation via fastboot flash? Every time ive flashed the images from the nvidia support site it bricked my device.
I have figured out how to roll back to Lollipop.
First download the ROM nv-recovery-image-shield-atv-upgrade2_1_dev_rooted.zip.
Next download twrp-multirom-20151112-UNOFFICIAL-foster.img.
Boot SATV into Fastboot.
Extract and flash staging blob, boot.img, system.img, userdata.img (this will wipe the internal storage) and dtb file.
Reboot back into Fastboot.
Flash TWRP then boot directly into recovery (do not reboot).
From TWRP mount system as read-write.
Use the file manager to navigate to /system/app/TegraOTA.
Delete all files within the folder TegraOTA.
Reboot normally and go through the first time setup wizard. SATV will not download the OTA update and remain on 5.1 Lollipop.
Despite the title saying 5.0.2, the current firmware downloads seem to be available here (including the dev_rooted version!) with no Nvidia developer account required:
http://www.techspot.com/drivers/driver/file/information/17759/ :good:
Problem recover.
Hello i dont know if i in the right Thread here.
I unlocked BOOTLOADER and installed lineage OS 15.1.
And decided that i wanted to go back to stock.
I dowloaded shield-atv-2017 and followed the fastboot guide and transfered all the img to my 2017 nvidia.
When i reboot the message appears that BOOTLOADER is unlocked and after a few sec it shows the nvidia logo and then nothing...
Please help me....
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Hello people.
Due to the fact that I have a tablet built around the MTK8127 SOC I decided to adapt some stuff for the Amazon Fire 2015
I need to mention that I don`t own the tablet so I don`t have the means to test the recovery.
The recovery is built from source using CM 12.1 and is based on the classic CWM with further additions designed for MTK devices like backup of important partitions (uboot. tee1, tee2 and so on)
What could be wrong:
-mounting points, as I used the default ones that are being used for twrp
-resolution (the recovery might not fit properly on the screen.
-other random stuff
Features
-full touch recovery
- all cwm functionalities (adb, sideload, backup, restore, install, mass storage...).
-in Carliv menu there is now a new section for flashing boot and recovery images.
-a special menu from where you can restore specific partitions
-multizip flashing function
The main sources used are here:
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/src
I have not uploaded yet the device tree that I am using as I don`t know if the build is actually working (it should), Will do when I have some days off from work .
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Credits to @carliv aka @bluefirebird for his efforts in continuing the CWM project in his new form as CTR.
globula_neagra said:
Hello people.
Due to the fact that I have a tablet built around the MTK8127 SOC I decided to adapt some stuff for the Amazon Fire 2015
I need to mention that I don`t own the tablet so I don`t have the means to test the recovery.
The recovery is built from source using CM 12.1 and is based on the classic CWM with further additions designed for MTK devices like backup of important partitions (uboot. tee1, tee2 and so on)
What could be wrong:
-mounting points, as I used the default ones that are being used for twrp
-resolution (the recovery might not fit properly on the screen.
-other random stuff
Features
-full touch recovery
- all cwm functionalities (adb, sideload, backup, restore, install, mass storage...).
-in Carliv menu there is now a new section for flashing boot and recovery images.
-a special menu from where you can restore specific partitions
-multizip flashing function
The main sources used are here:
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/src
I have not uploaded yet the device tree that I am using as I don`t know if the build is actually working (it should), Will do when I have some days off from work .
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Credits to @carliv aka @bluefirebird for his efforts in continuing the CWM project in his new form as CTR.
Click to expand...
Click to collapse
For awareness:
- this (any) custom recovery can only be started from fastboot on devices with 5.0.x bootloaders (rather rare)
- no custom recovery can be flashed (installed) on this device as bootloader remains locked.
globula_neagra said:
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Click to expand...
Click to collapse
Thanks for your work but... no one will flash this because it's impossible on Fire due to the locked bootloader. People with the 5.0.1-based fastboot implementation will be able to boot it but not to flash it. I will try it and report back as I use this recovery on my MTK-base Asus and I love it.
A bootloader downgrade should be achievable with SP flash tools.
Are there any bootloaders uploaded somewhere ?
globula_neagra said:
A bootloader downgrade should be achievable with SP flash tools.
Are there any bootloaders uploaded somewhere ?
Click to expand...
Click to collapse
Have a look at the various threads in the different sections of the "Amazon Fire" forum. There are some downgrade protections from Amazon on these devices and hard bricks are unfortunately not so difficult.
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
globula_neagra said:
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
Click to expand...
Click to collapse
Partial responses:
- no one has successfully flashed twrp or any other custom recovery
- a custom recovery could be booted from fastboot on early devices; the 'vulnerability' was closed with bootloader 5.1.x and above
- bootloaders 5.1.x+ can not be rolled back to 5.0.x; hard brick
- Amazon rollback efuse has proven to be fairly robust; was never cracked on 3rd/4th gen devices that enjoyed a 2+ year run (albeit on a different chipset)
globula_neagra said:
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
Click to expand...
Click to collapse
We don't have .auth file for authentication. SP Flash tool useless without it (we can't even readback). We have secured chip.
*delete thread*
Please...?
?
quick review:
recovery boot fine
resolution seems to be off
buttons don't work
touch screen is off
sd_shadow said:
quick review:
recovery boot fine
resolution seems to be off
buttons don't work
touch screen is off
Click to expand...
Click to collapse
Sounds like a home run
How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.
reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.
My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.
Used funky
mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.
Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.
diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?
Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.