Related
Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?
If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk
Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps
Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....
you need root to use the recovery updater.
download the recovery image and flash it in fastboot
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?
Sure, ASAP
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...
sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.
Thank you anyway
You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.
Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]
That totally solved the problem
Thank you ALL!!!
sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks
htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!
Hopefully someone is able to help...
I had my tmo moto x unlocked with twrp and root and I tried a factory reset through the twrp recovery and it erased all the software. It booted to the setup screen where I proceeded to log in with Google but it didn't work I think and when it got the home screen it just showed a loading circle and that's it and stupid me I didn't make a backup before
I've tried using the tool in the android development thread to flash back to stock but now my phone doesn't even boot at all I can get to the bootloadwr and I can successfully flash files through the Motorola tool by removing the proper line in the XML file but my phone still don't boot
It just flashes the little android laying down and says error every 5 seconds I don't know what to do anymore I've searched all over and no matter what I can't get the phone to boot
Thanks for the help if any
1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.
nhizzat said:
1. With an unlocked bootloader, you're not fully bricked if you can get to the bootloader.
2. Download the SBF file for your variant here http://sbf.droid-developers.org/phone.php?device=0. If you're already on the 4.4.2 bootloader, download only the 4.4.2 SBF file.
3. Learn how to use fastboot/mfastboot and adb. Follow the steps in the "return to stock" section here http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358.
4. Extract the SBF file, boot into the bootloader, type what's in the "return to stock" section verbatim. Skip the fastboot oem lock step though and don't copy/paste.
5. Stop using toolboxes and scripts until you understand how fastboot and adb work. They'll save your ass each and every time.
Click to expand...
Click to collapse
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help
genaro12543 said:
thank you so much for the help but for some reason when i flash the files to my device they run the process perfectly fine but when the phone boots its still doing the same thing where it just flashes the android on his back for like a second every five seconds or so. I did the 4.4.2 update first then i tried 4.2.2 just to give it a shot but i dont think that flashed right since its says an error about downgrading the security in the bootloader
please if there are any other suggestions im open ears ive searched everywhere and tried everything but i still cant get the phone to actually boot up at all
thanks for the help
Click to expand...
Click to collapse
once you've upgraded to 4.4.2, you can't go back to 4.2.2.
as mentioned, download the 4.4.2 fastboot files and flash each partition.
make sure to wipe data and cache once all partitions are flashed.
here are some more notes regarding flashing:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
imp3r10 said:
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
Click to expand...
Click to collapse
Indeed and before rebooting , you MUST Wipe Data + Internal Storage, cuz you are flashing new boot and system and will get in conflicts if there no wipe.
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
runderekrun said:
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
Click to expand...
Click to collapse
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
peramikic said:
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
Click to expand...
Click to collapse
Thanks.
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
runderekrun said:
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
Click to expand...
Click to collapse
Step 6 to pull your own: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Or you can download the one I pulled from my device (it can be found in the Mega folder linked in the OP): http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
And as option 3 it's inside the B18toB20 OTA file floating somewhere around here
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
runderekrun said:
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
Click to expand...
Click to collapse
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
peramikic said:
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
Click to expand...
Click to collapse
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
runderekrun said:
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
Click to expand...
Click to collapse
Yeah, now that we know fastboot will work even on stock boot that will work as well. The only thing you won't be able to do is flash back the B20 fastboot image that way, but enough to pass OTA most likely. The long way you can revert the fastboot image as well. I only wanted to post the image to begin with, but then wrote out instruction as they rolled around in my head. This will change soon anyways so a proper write-up will happen, just not by me, Documentation was never my forte
My BL is unlocked from ZTE right now, If I want to get CM for future but also want upcoming update from ZTE? What are the exact steps that I need to follow to get future OTA but also keep the BL unlocked for future CM? Please help as I'm confused with all these instructions.
peramikic said:
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
Click to expand...
Click to collapse
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
seby1234 said:
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
Click to expand...
Click to collapse
All right I'm no expert either but I'll try to make this as straightforward as possible.
1) Format your SD card as exFAT. This is important as otherwise you will not be able to transfer the system image to your SD card since it is 6GB. To do this you can just plug it in to your PC, right click, Format and then select exFAT from the dropdown.
2) Download tenfar's tool for B20, rczrider's boot and recovery backup, and the system image backup from the link in the OP.
3) Create a new folder in /external_sd/TWRP/BACKUPS/serial_number/.Move the stock_boot_backup and stock_recovery backup into the folder.
4) Using a program such as 7zip, extract the 6GB system image file and move it to the same folder.
6) Go to into fastboot mode. Before you do anything you have to relock the bootloader otherwise the system will be modified and you want to be 100? stock. Execute 'fastboot oem lock'. You should then boot to a black screen.
7) Unzip tenfar's tool. Go to the unzipped folder, then hold down shift+right click and select 'Open command window here'. Execute 'axon7root.exe -p [COMPORT #] -r. To figure out your com port #, go to Device Manager, then go to down to where it says "Qualcomm Loader..." and your com port number is the number at the end. So for example if your com port number is 5, you should execute axon7root.exe -p 5 -r. Allow the program to do its thing.
5) Boot into TWRP. Do not swipe to allow modifications. Once in TWRP, go to "Install", "Install Image" at the bottom right hand corner, and then navigate to the stock_recovery_backup in the folder that you moved it to to. Select it and then choose the Recovery partition to flash it to. Do the same thing for stock_boot_backup.
6) Once you have flashed boot and recovery, go to the main menu, then "Restore" and then Restore the system image backup.
7) Go to wipe and then slide to factory reset. Finally, reboot system.
Hope that helps! If you have any questions, feel free to ask me.
rczrider's stock boot and recovery thread
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818/page7
tenfar's tool thread: http://forum.xda-developers.com/axo...xon-7-root-bootloader-unlokced-t3441204/page1
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
shifuharris said:
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
Click to expand...
Click to collapse
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Quick question for anyone who might know.
The Link to system image which is : https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy has the following;
1. system_image.emmc.win
2. system_image.emmc.win.md5
Am I suppose to rename system_image.emmc.win to system_image.emmc.img and load?
it's not as clear that's why I ask but I ended up downloading rczrider system.img and reflashed via TWRP since I was a bit confused.
Thanks!
***************
I simply just went into TWRP backed up by boot so it would create a directory that contains the info I needed copied the system_image.emmc.win and system_image.emmc.win.md5 and restored.
xtermmin said:
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Click to expand...
Click to collapse
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
shifuharris said:
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
Click to expand...
Click to collapse
Try the microSD card method instead.
First, make sure OEM Unlocking is checked in developer settings, rename the OTA to "update.zip", put on microSD, boot into stock recovery, and choose update from microSD.
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/
First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:
A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.
PC/Linux: $ adb reboot bootloader
A2 boots into boot loader.
PC/Linux: $ fastboot oem unlock
Then I tried installing Magisk:
A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).
PC/Linux: $ adb reboot recovery
A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.
A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.
A2 boots into recovery.
A2/Recovery: Selected Apply update from ADB.
PC/Linux:
$ adb sideload Magisk-v16.0.zip
Total xfer: 1.01x
A2/Recovery: Error message failed to verify whole-file signature
PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.
What else can I try?
PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.
You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Didgeridoohan said:
You can't sideload the Magisk zip on a stock recovery.
Click to expand...
Click to collapse
Thanks!
If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Click to expand...
Click to collapse
Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):
I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)
I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)
I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.
To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0
Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.
Phew, for now I’m out of options, and I’ve a non functioning device.
In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.
The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.
PS: Sorry about the confusion with all those numbers.
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Didgeridoohan said:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Click to expand...
Click to collapse
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:
flash_all_except_data.sh
flash_all.sh
flash_all_lock.sh
flash_all_lock_crc.sh
The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py
Here’s how I got back to a system that boots up fine:
PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Following this success, I did another attempt at installing Magisk:
PC/Linux: $ cp ../patched_boot.img images/boot.img
(created with Magisk Manager from the V9.6.10.0 boot.img)
PC/Linux: $ python2.7 flash_gen_crc_list.py
(thought it’s a good idea, but doesn’t help – see below)
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Unfortunately, upon reboot I get:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.
Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!
Any idea?
Uh-oh! Now it seems like I eclipsed my previous stupidity.
In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.
As result, I get the aforementioned error message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)
Bricked for good, right? :crying:
Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).
Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...
If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.
That sucks... I hope you get things sorted. Good luck.
Didgeridoohan said:
Now I wished I would have had the time, […]
Click to expand...
Click to collapse
Don’t worry. I like to take systems to their limit.
[…] since I would have posted that you should never lock your bootloader on a modded device.
Click to expand...
Click to collapse
For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.
I wonder if I would also get the your device is corrupt message with Lineage installed.
If you're lucky there's still some kind of hack available
Click to expand...
Click to collapse
Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)
feklee said:
I wonder if I would also get the your device is corrupt message with Lineage installed.
Click to expand...
Click to collapse
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Didgeridoohan said:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Click to expand...
Click to collapse
No:
I’m almost certain that I did not enable dm-verity.
The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.
BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…