Think new thread needs to be started too separate the different hardware configurations of the htc 626 this is for the a32_ul hardware with Qualcomm snapdragon 410 4 core 64bit activated hardware.
as the htc626s has rooting method that is not compatible to the a32_ul type as the htc 626 has a Qualcomm Snapdragon 210 hardware.
This Thread is for HTC 626 A32_UL Qualcomm snapdragon 410 :good:
I am not able to make a twrp recovery for the htc626 a32_ul phone type , i have looked at uncompiled images of boot and recovery images and see such image learning path that i doubt i am capable to build such custom rom or method to root this phone myself, so started this thread to one separate the rooting method of htc626s and to encourage others that more able than me to create a custom rom for the htc 626 a32_ul chip-set
.
Custom Recovery(s) for a32_ul Desire 626
So I managed to get two image files and when doing the fastboot boot command, it didn't display the error for not having a dtb as the recovery is rebuilt for this device (as far as I can see anyway). I flashed each file as well to try each of them that way instead of the boot command as the boot command just froze the phone and both gave the same result. It will boot into recovery mode but will have a blank screen and not do anything.
I'll link the files download links, as well as the source as to where I downloaded the files here below. All credit should go to the creators of the files.
Try them out and see if you can get them working yourself.
As a note, I am unable to post links due to the account type I have as it is now so put mediafire before those links with a forward slash. Also, one is for TWRP 2.8.0.0 and one is 2.8.7.0. Anyway...
?ubuhbdj0ygdkcqb
and
?bviw88iyrgmyef8
Source: type twrp a32_ul into google and it will be on the website known as ai-development
Good luck and let me know if you make any progress with these.
Is the A32_UL belong to the Desire 626x ???
yes i the 626x is version that came with android 4.4.4 and i think was 32bit
the latest version in europe is htc 626 a32ul_emea and is 64 bit with android 5.1
frankgambit said:
yes i the 626x is version that came with android 4.4.4 and i think was 32bit
the latest version in europe is htc 626 a32ul_emea and is 64 bit with android 5.1
Click to expand...
Click to collapse
i have made copy of htc a32_ul android 5.1 android qualcomm 410 chipset system directory, i have treid almost every way i can think to make a system.img file to make emulator so to then make a twrp recovery.img , and tried everything i can to cook such file, but without success, i can upload copy of system file for anyone to use, i just want a working system.img file to work with to make a recovery.img, or some sort update.zip that give me access to root commands to this phone.
all i have is copy of the system directory., and can copy any other files now that needed from phome that needed to make system.img or update.zip, but dont know how at moment to continue without help or i flucik it out some time
any help i be glad of thanks
regards frankgambit
Guys I found this, and it worked!!!
http://forum.xda-developers.com/des...htc-desire-t3264727/post64390390#post64390390
ByronFer said:
Is the A32_UL belong to the Desire 626x ???
Click to expand...
Click to collapse
yes.. check with cpu-z.. It clearly shows that
ByronFer said:
Guys I found this, and it worked!!!
http://forum.xda-developers.com/des...htc-desire-t3264727/post64390390#post64390390
Click to expand...
Click to collapse
Didn't manage to root my device using that instructions... device - a32_ul, A-5.1 build 1.09.401.6
Downloaded and flashed the twrp recovery downloaded from here as per the OPs post,
http://www.Mediafire.com/?bviw88iyrgmyef8
but as stated by OP all I get is a blank screen. These recovery images are obviously intended for the 32 bit variant and not the 64bit..... Now I need a stock UL32-EMEA to reflash my recovery....
you will find reccovery_signed.img and boot signed.img to get back to stock for htc 626 a32_ulk-emea 64bit android 5.1 from link below
https://drive.google.com/file/d/0B4Xp3GIFBvPvb1ZoTmQ2MnkzT2c/view?usp=sharing
gl
frankgambit said:
you will find ewcovery_signed.img and boot signed.img to get back to stock for htc 626 a32_ulk-emea 64bit android 5.1 from link below
https://drive.googe.com/file/d/0B4Xp3GIFBvPvb1ZoTmQ2MnkzT2c/view?usp=sharing
gl
Click to expand...
Click to collapse
missed the L out of google
https://drive.google.com/file/d/0B4Xp3GIFBvPvb1ZoTmQ2MnkzT2c/view?usp=sharing
frankgambit said:
you will find reccovery_signed.img and boot signed.img to get back to stock for htc 626 a32_ulk-emea 64bit android 5.1 from link below
https://drive.google.com/file/d/0B4Xp3GIFBvPvb1ZoTmQ2MnkzT2c/view?usp=sharing
gl
Click to expand...
Click to collapse
Thanks for that Frank.
Slight issue tho, unless I am being really stupid,
When I extract the recovery_signed.img file from the zip, it comes out at 28.6mb, when I try to flash it Fastboot errors .
C:\ADB>fastboot flash recovery recovery_signed.img
target reported max download size of 16773120 bytes
Invalid sparse file format at header magi.
What am I missing. I presume that my recovery partition is only 16mb?
Alsajosora said:
Thanks for that Frank.
Slight issue tho, unless I am being really stupid,
When I extract the recovery_signed.img file from the zip, it comes out at 28.6mb, when I try to flash it Fastboot errors .
C:\ADB>fastboot flash recovery recovery_signed.img
target reported max download size of 16773120 bytes
Invalid sparse file format at header magi.
What am I missing. I presume that my recovery partition is only 16mb?
Click to expand...
Click to collapse
you are useing incorrect fastboot version i use this one https://drive.google.com/file/d/0B4Xp3GIFBvPvSjdZOUxHV05vTWM/view?usp=sharing
frankgambit said:
you are useing incorrect fastboot version i use this one https://drive.google.com/file/d/0B4Xp3GIFBvPvSjdZOUxHV05vTWM/view?usp=sharing
Click to expand...
Click to collapse
That one flashed ok. Now I can boot to recovery but all I have is a red triangle with and exclamation mark?
Do I need to flash the boot.img file as well?
Many thanks for your help!!!
Alsajosora said:
That one flashed ok. Now I can boot to recovery but all I have is a red triangle with and exclamation mark?
Do I need to flash the boot.img file as well?
Many thanks for your help!!!
Click to expand...
Click to collapse
when u got red triangle u in recovery mode , u then have to press vol up and power buttons for 3 sec apx at same time to get into recovery menu it takes few presses to get right sometimes .
LOL,
just googled and already there!!!
Many thanks for all your help Frank!!!
vlstr said:
Didn't manage to root my device using that instructions... device - a32_ul, A-5.1 build 1.09.401.6
Click to expand...
Click to collapse
Thats weird, my phone is a 626x and its a32_ul as well but cant say if its x64 and managed to root it without trouble.. :cyclops: :cyclops:
ByronFer said:
Thats weird, my phone is a 626x and its a32_ul as well but cant say if its x64 and managed to root it without trouble.. :cyclops: :cyclops:
Click to expand...
Click to collapse
Check what CPU Z says about your phone version.
BTW - what img recovery have you used for flashing and rooting?
a32ul_emea here too.... snapdragon 400/410, android 5.1, kernel architechture aarch64... and recovery using previous link lead to black screen...
someone found a working recovery for our phone ? ^^
Related
Hello Guys,
pls help me, just working around for about 3 hours...
I try to flash my system.img in order to flash the KIT KAT Rom in Stock recovery (because of error:"system/app/EMailGoogle.apk" has unexpected content" => installation aborted; i red about the tipp to flash the system.img)
Having the system.img in the same directory as fastboot.exe and adb.exe it doesnt work unfortunately...
With command fastboot devices i do see my HTC ONE
fastboot flash recovery recovery.img does work fine
fastboot flash recovery system system.img doesnt work! error: cannot load system.img => Same directory
I downloaded it twice (may be bad download)
What i am doing wrong?
Greets and thanks for helping me ....
the system.img is too large. Can't be flashed unless it's zipped.
trouble0 said:
Hello Guys,
pls help me, just working around for about 3 hours...
I try to flash my system.img in order to flash the KIT KAT Rom in Stock recovery (because of error:"system/app/EMailGoogle.apk" has unexpected content" => installation aborted; i red about the tipp to flash the system.img)
Having the system.img in the same directory as fastboot.exe and adb.exe it doesnt work unfortunately...
With command fastboot devices i do see my HTC ONE
fastboot flash recovery recovery.img does work fine
fastboot flash recovery system system.img doesnt work! error: cannot load system.img => Same directory
I downloaded it twice (may be bad download)
What i am doing wrong?
Greets and thanks for helping me ....
Click to expand...
Click to collapse
Is there a tutorial that i can follow ?
Im afraid there s no easier way to update my One GPE 4.3 because of that error
ipfreelytech said:
the system.img is too large. Can't be flashed unless it's zipped.
Click to expand...
Click to collapse
trouble0 said:
Is there a tutorial that i can follow ?
Im afraid there s no easier way to update my One GPE 4.3 because of that error
Click to expand...
Click to collapse
what exactly is that "system.img" you are trying to flash?
I converted my HTC ONE a half a year ago into a GPE ONE.
I used the GPE RUU 4.3 and flashed my HTC with fastboot; changed also model id and cid...
Im afraid but i cannot post the link to that tutorial.
Just type in on google search "Convert HTC ONE Google Edition android wonder how to" and click on the first one...
I think this file is the normal 4.3 GPE RUU! But in this file there is also an system.img... i thought it is the right one to flash ?!
nkk71 said:
what exactly is that "system.img" you are trying to flash?
Click to expand...
Click to collapse
Have you checked for OTA ? Also remember that lots of people are having issues with 4.4, and if you already have an issue with recovery, might not be a good idea to go with 4.4 right now.
SaHiLzZ said:
Have you checked for OTA ? Also remember that lots of people are having issues with 4.4, and if you already have an issue with recovery, might not be a good idea to go with 4.4 right now.
Click to expand...
Click to collapse
Yeah OTA doesnt work too, same Problem (unexptected content; installation aborted)
May be i should wait a bit ... at the moment cannot do an OTA because 4.3 seems to be actual ...
I've got this phone from rogers, its been stuck in a boot loop, and I am trying to get the ruu to revert it to stock. The one on HTC's website doesn't work. Can anyone help me?
mur1taza said:
I've got this phone from rogers, its been stuck in a boot loop, and I am trying to get the ruu to revert it to stock. The one on HTC's website doesn't work. Can anyone help me?
Click to expand...
Click to collapse
It does work. Your problem is you need to relock the bootloader if you unlocked it and you also 100% need the stock recovery image because if you have Philz Touch Recovery installed it's going to block the RUU from working and that's part of HTC's security measures.
Re
MrMike2182 said:
It does work. Your problem is you need to relock the bootloader if you unlocked it and you also 100% need the stock recovery image because if you have Philz Touch Recovery installed it's going to block the RUU from working and that's part of HTC's security measures.
Click to expand...
Click to collapse
I tried relocking the bootloader and used the ruu but I got an error 155, they said I had the wrong image. I have TWRP recovery installed. And the device wont even boot into that. How do I get the stock image?
mur1taza said:
I tried relocking the bootloader and used the ruu but I got an error 155, they said I had the wrong image. I have TWRP recovery installed. And the device wont even boot into that. How do I get the stock image?
Click to expand...
Click to collapse
First you need to find out whether or not your phone is 32 or 64 bit so remove the battery and replace it then hold the volume down button and press the power button at the same time then type everything you see on your HBoot screen here so I can see it.
MrMike2182 said:
First you need to find out whether or not your phone is 32 or 64 bit so remove the battery and replace it then hold the volume down button and press the power button at the same time then type everything you see on your HBoot screen here so I can see it.
Click to expand...
Click to collapse
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.0822
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
mur1taza said:
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.0822
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Click to expand...
Click to collapse
Go over here to twrp website twrp 2.8.7.0 HTC Desire 510 then make sure this image file downloads into your minimal adb and fastboot folder on the computer and it MUST be inside the folder then open a command window within the folder and try flashing the recovery file but first change the name I.E rename the file to recovery.img and then do fastboot flash recovery recovery.img after that type adb reboot recovery and see if it worked.
MrMike2182 said:
Go over here to twrp website twrp 2.8.7.0 HTC Desire 510 then make sure this image file downloads into your minimal adb and fastboot folder on the computer and it MUST be inside the folder then open a command window within the folder and try flashing the recovery file but first change the name I.E rename the file to recovery.img and then do fastboot flash recovery recovery.img after that type adb reboot recovery and see if it worked.
Click to expand...
Click to collapse
I tried that, the fastboot command returned a reply that said finished. After I tried the adb reboot recovery command it returned "error: device '(null)' not found"
mur1taza said:
I tried that, the fastboot command returned a reply that said finished. After I tried the adb reboot recovery command it returned "error: device '(null)' not found"
Click to expand...
Click to collapse
Download this one then and flash it then try to get into recovery... philz touch recovery
MrMike2182 said:
Download this one then and flash it then try to get into recovery... philz touch recovery
Click to expand...
Click to collapse
I tried that too, it did the same thing.
mur1taza said:
I tried that too, it did the same thing.
Click to expand...
Click to collapse
I don't know then. I don't have enough information about it to help. Don't know if you are 32 or 64 bit. Don't know if you have a stock recovery I really don't know much. I'm pretty sure you're not doing something right... Go over the steps of everything you've done so far please.
MrMike2182 said:
I don't know then. I don't have enough information about it to help. Don't know if you are 32 or 64 bit. Don't know if you have a stock recovery I really don't know much. I'm pretty sure you're not doing something right... Go over the steps of everything you've done so far please.
Click to expand...
Click to collapse
I think its 32 bit. I had previously tried TWRP to install a custom rom and it worked. Now that I want to revert to stock Im getting this error in adb.
mur1taza said:
I think its 32 bit. I had previously tried TWRP to install a custom rom and it worked. Now that I want to revert to stock Im getting this error in adb.
Click to expand...
Click to collapse
What is the exact error you are getting in adb? I need the exact way you see it.
MrMike2182 said:
What is the exact error you are getting in adb? I need the exact way you see it.
Click to expand...
Click to collapse
I finally got to get into TWRP recovery, what do I do now?
mur1taza said:
I finally got to get into TWRP recovery, what do I do now?
Click to expand...
Click to collapse
You need to download a rom and flash it... You can try whichever roms on here you want since your phone is 32 bit.. CM11 is good and so is RaptorRom.. But you can use whatever as long AS it IS for the Desire 510... Download a rom, place it on your SD card and go into recovery an tap install and choose the rom that you put on the SD card... Make sure you read the thread of whichever rom you download since some need a specific Kernel or wifi fix.. Also some times twrp will be set to internal storage and you will need to select the SD storage at the top of the window after you tap install...
MrMike2182 said:
You need to download a rom and flash it... You can try whichever roms on here you want since your phone is 32 bit.. CM11 is good and so is RaptorRom.. But you can use whatever as long AS it IS for the Desire 510... Download a rom, place it on your SD card and go into recovery an tap install and choose the rom that you put on the SD card... Make sure you read the thread of whichever rom you download since some need a specific Kernel or wifi fix.. Also some times twrp will be set to internal storage and you will need to select the SD storage at the top of the window after you tap install...
Click to expand...
Click to collapse
Thanks a lot! And if I want to revert to stock what do I do?
mur1taza said:
Thanks a lot! And if I want to revert to stock what do I do?
Click to expand...
Click to collapse
Just download a stock rom from one of the threads.
After Flashing This Stock Rom you will still receive ota Updates Without Any Error!!!
Android One G1 Stock Rom Fastboot Flashable - This is 100% Working and Tested before posting
Things Needed :
A Laptop/Desktop
ADB and Fastboot Drivers Installed (If you dont have one you can check it here - http://forum.xda-developers.com/showthread.php?t=2588979 - 15 Seconds ADB Installer)
The Downloaded Android One G1 Stock Rom (LUZ59M) - http://www.mediafire.com/download/6shl7b41fzdaku4/Android_One_G1_Stock_Rom_Fastboot_(LUZ59M).zip. kalvin is the PASSWORD of the Zip/ROM
Procedure :
1. Download The Stock Rom and Extract it any location on your Laptop/Desktop.
2. Boot your Android One G1 to Fastboot mode.
How to Boot To Fastboot Mode?
( Volume Down + Power Button ) - Release it when you see the G1 logo (you will have to stuck on G1 logo that means you successfully booted to fastboot)
For Cyanogen Os Users Use the (Advance reboot to Bootloader or Volume Up + Power) there will be a screen notification that you are on a fastboot mode
Next option if you cant manually boot to fastboot just plug your G1 to pc/laptop (properly booted/Nka open)
make sure you installed the drivers properly after you plug the phone Just run the bat file and it will boot your phone to fastboot mode and the Rom Installation Will Begin
Just Run The .Bat file i created and the installation is all Automated
Notice : If an ERROR is prompt after the splash.img before the System.img flashing just ignored it , the installation still continues and running dont unplug your phone just wait it until your phone Reboots and its all done you are now on STOCK ROM LUZ59M Build ( Dont Worry if you Encounter An Error While Flashing ,the rom will be installed properly ) i just encounter this when you are from a cyanogen OS Rom
Do a Factory Reset After you Booted the ROM Properly
Credits to :
ME
August
JoeyHuab
MeteBerkErgun/Sadronis
Snoop05(xda) - 15 seconds adb/fastboot installer
To All my Fellow AndroidOne Admins 1st Gen & 2nd Gen
Enjoy and Goodluck!!!! - Kalvin/KShen
kalvin026 said:
After Flashing This Stock Rom you will still receive ota Updates Without Any Error!!!
Android One G1 Stock Rom Fastboot Flashable - This is 100% Working and Tested before posting
Things Needed :
A Laptop/Desktop
ADB and Fastboot Drivers Installed (If you dont have one you can check it here - http://forum.xda-developers.com/showthread.php?t=2588979 - 15 Seconds ADB Installer)
The Downloaded Android One G1 Stock Rom (LUZ59M) - http://www.mediafire.com/download/6shl7b41fzdaku4/Android_One_G1_Stock_Rom_Fastboot_(LUZ59M).zip. kalvin is the PASSWORD of the Zip/ROM
Procedure :
1. Download The Stock Rom and Extract it any location on your Laptop/Desktop.
2. Boot your Android One G1 to Fastboot mode.
How to Boot To Fastboot Mode?
( Volume Down + Power Button ) - Release it when you see the G1 logo (you will have to stuck on G1 logo that means you successfully booted to fastboot)
For Cyanogen Os Users Use the (Advance reboot to Bootloader or Volume Up + Power) there will be a screen notification that you are on a fastboot mode
Next option if you cant manually boot to fastboot just plug your G1 to pc/laptop (properly booted/Nka open)
make sure you installed the drivers properly after you plug the phone Just run the bat file and it will boot your phone to fastboot mode and the Rom Installation Will Begin
Just Run The .Bat file i created and the installation is all Automated
Notice : If an ERROR is prompt after the splash.img before the System.img flashing just ignored it , the installation still continues and running dont unplug your phone just wait it until your phone Reboots and its all done you are now on STOCK ROM LUZ59M Build ( Dont Worry if you Encounter An Error While Flashing ,the rom will be installed properly ) i just encounter this when you are from a cyanogen OS Rom
Do a Factory Reset After you Booted the ROM Properly
Credits to :
ME
August
JoeyHuab
MeteBerkErgun/Sadronis
Snoop05(xda) - 15 seconds adb/fastboot installer
To All my Fellow AndroidOne Admins 1st Gen & 2nd Gen
Enjoy and Goodluck!!!! - Kalvin/KShen
Click to expand...
Click to collapse
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!
kalvin026 said:
Just Run The .Bat file i created and the installation is all Automated
Click to expand...
Click to collapse
Where is the .bat file?
vel_tins said:
Where is the .bat file?
Click to expand...
Click to collapse
Look for Windows Batch File
---------- Post added at 06:43 AM ---------- Previous post was at 06:41 AM ----------
gabrieladrian said:
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!
Click to expand...
Click to collapse
Yes. The build number LMY refers to a marshmallow build.
rho57 said:
Look for Windows Batch File
Click to expand...
Click to collapse
?
Again, where is the .bat file, mentioned in the first post?
vel_tins said:
?
Again, where is the .bat file, mentioned in the first post?
Click to expand...
Click to collapse
Dude. Did you even at least download the stock dump? Everything that's needed is in that zipped package. Don't go around asking where the bat file because everything's in there. I'm guessing that either you haven't seen what's inside the package, or you're just lazy enough to look for it.
Better yet, learn how to flash factory images manually so you don't have to ask where that stupid bat file is anymore.
rho57 said:
Dude. Did you even at least download the stock dump? Everything that's needed is in that zipped package. Don't go around asking where the bat file because everything's in there. I'm guessing that either you haven't seen what's inside the package, or you're just lazy enough to look for it.
Better yet, learn how to flash factory images manually so you don't have to ask where that stupid bat file is anymore.
Click to expand...
Click to collapse
Seem to me that some people in this forum have short fuses. Cool down and hold your horses tight. There's no need for unnecessary and inflammatory rhetorics.
ondoy1943 said:
Seem to me that some people in this forum have short fuses. Cool down and hold your horses tight. There's no need for unnecessary and inflammatory rhetorics.
Click to expand...
Click to collapse
First of all, I don't care about your opinion. Secondly, you had the choice to help him find the bat file, but instead criticized the way I post. I don't see the point in that.
rho57 said:
First of all, I don't care about your opinion. Secondly, you had the choice to help him find the bat file, but instead criticized the way I post. I don't see the point in that.
Click to expand...
Click to collapse
Think your post as a ball; I'll hit it with a bat, and return it to you. Ha..ha. Lol...
ondoy1943 said:
Think your post as a ball; I'll hit it with a bat, and return it to you. Ha..ha. Lol...
Click to expand...
Click to collapse
Go find somebody else to troll.
inside the zip
vel_tins said:
Where is the .bat file?
Click to expand...
Click to collapse
the bat file is inside the zip file, many already tried this dump , and i will sure to you that this will work
yes 100% sure
gabrieladrian said:
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!
Click to expand...
Click to collapse
yes 100% sure but first you need to have an unlocked bootloader to do fastboot
kalvin026 said:
yes 100% sure but first you need to have an unlocked bootloader to do fastboot
Click to expand...
Click to collapse
Hi @kalvin, and a Happy new Year to you and all fellow followers of the 2nd gen android one devices. Mine is Cherry Mobile H220, I want to try going back from MM to the zip you posted. Would it be Lazy of me, if I asked you to supply the order of commands I need to get The Zip LUZ59M into the H220?. I have adb /fastboot prog running ok now(I think). In Device manager it shows that I have the necessary drivers installed, Android Composite ADB interface at top, and further down in list Portable Devices shows H220..Phone shows usb debugging connected and usb for file transfer(mtp), (in the dropdown notification list).,So, awaiting maybe a reply from you, Wish I had experimented with version 5.1.1 lollipop, before I accepted last OTA major update,,I,m a real newbie to android one devices, but have used MTK socs before with always success. The adb /fastboot thingy is a new adventure for me. I like this H220 device and dont want to ruin it,. Thank you for your time,, and to you @ vel-tins for answering my last post in another thread, The Xmas holiday period sort of held things up a bit, bending my elbow too much,LOL.....
Sockit2me said:
Hi @kalvin, and a Happy new Year to you and all fellow followers of the 2nd gen android one devices. Mine is Cherry Mobile H220, I want to try going back from MM to the zip you posted. Would it be Lazy of me, if I asked you to supply the order of commands I need to get The Zip LUZ59M into the H220?. I have adb /fastboot prog running ok now(I think). In Device manager it shows that I have the necessary drivers installed, Android Composite ADB interface at top, and further down in list Portable Devices shows H220..Phone shows usb debugging connected and usb for file transfer(mtp), (in the dropdown notification list).,So, awaiting maybe a reply from you, Wish I had experimented with version 5.1.1 lollipop, before I accepted last OTA major update,,I,m a real newbie to android one devices, but have used MTK socs before with always success. The adb /fastboot thingy is a new adventure for me. I like this H220 device and dont want to ruin it,. Thank you for your time,, and to you @ vel-tins for answering my last post in another thread, The Xmas holiday period sort of held things up a bit, bending my elbow too much,LOL.....
Click to expand...
Click to collapse
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
rho57 said:
fastboot flash aboot emmc_appsboot.mbn
@rho57, Thanks for answer friend, but my question was meant to be, What adb commands do I use in Minimal adb and fastboot, , Anyway I,ve managed to get Luz59m into the H220, but I seem to be stuck in a bootloop situation?, The 4 moving colours are there now, which suggests Android 5,1,1 is in the phone,Then says android is starting, then maybe 101 apps need optimizing, then back to the same colours rotateing, and back to optimizing apps, (said 82 second time), now optimizing again 101, , oh dear, need help now on what went wrong?. Any ideas?..Thanks.
Click to expand...
Click to collapse
^^
Have you tried a factory reset from recovery?
vel_tins said:
^^
Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
@Vel-tins. I think your referring to my last post, no I did not, slipped up on thinking about recovery, but anyway my Cherry Mobile is now a IQ2II, running 5.1.1. LUZ59Q.lol, seems to be ok, its asking me to update to the latest MM, might go back to MM after I play about a bit with Lollipop. Thanks for answering.
good day sir .. should i root first my phone H220 before to flash this rom? thank you
jsab20 said:
good day sir .. should i root first my phone H220 before to flash this rom? thank you
Click to expand...
Click to collapse
@jsab20, No need to root H220 first, I imagine your already in MM 6.0.1 version, (mmb29k). I did not wish to root,because of losing OTA upgrades, Anyway, I failed at first attempt,probably by not going into recovery,and rebooting. I downloaded version IQII from another thread by mrdmacdonald, , done exactly as he recommended and then I had successfully downgraded to 5.1.1. (luz59I), As soon as it installed it downloaded 3 updates,(wifi on) then asked if I wanted The MM major upgrade., I refused that update, till I want to go back to it later,..Go to thread I-Mobile IQII OTA URLs,, post number #20...If you try those instructions and succeed, you will have your H220 looking like an IQII on first screen,..Hope this helps my friend, good luck.
Sockit2me said:
@jsab20, No need to root H220 first, I imagine your already in MM 6.0.1 version, (mmb29k). I did not wish to root,because of losing OTA upgrades, Anyway, I failed at first attempt,probably by not going into recovery,and rebooting. I downloaded version IQII from another thread by mrdmacdonald, , done exactly as he recommended and then I had successfully downgraded to 5.1.1. (luz59I), As soon as it installed it downloaded 3 updates,(wifi on) then asked if I wanted The MM major upgrade., I refused that update, till I want to go back to it later,..Go to thread I-Mobile IQII OTA URLs,, post number #20...If you try those instructions and succeed, you will have your H220 looking like an IQII on first screen,..Hope this helps my friend, good luck.
Click to expand...
Click to collapse
@Sockit2me ..pardon me sir for asking many question cuz its my first time to handle an andriod one device and flashing using a fastboot is a new experience to me , my previous phone was a MTK device .. Yes i already upgraded to MMB29K over-the-air . I installed adb fastboot installer , and its already running , on my phone i enable usb debugging and oem unlock but when i try to flash a twrp it gets error and cannot load:crying:.. can u pls help me how to get on this ,thank you sir :good:
Hello
I needed recovery stock HTC désire 626 a32ul EMEA (europe)
Thanx
_p1x3l said:
Hello
I needed recovery stock HTC désire 626 a32ul EMEA (europe)
Thanx
Click to expand...
Click to collapse
Also looking for that, if anyone could help highly appreciated.
vlstr said:
Also looking for that, if anyone could help highly appreciated.
Click to expand...
Click to collapse
That would make three of us then...
Have you guys flashed the TWRP recovery that is on this site?
I did and now cannot get into recovery and when my phone is off but plugged into charge the battery animation doesn't work.....
me too....
Alsajosora said:
That would make three of us then...
Have you guys flashed the TWRP recovery that is on this site?
Click to expand...
Click to collapse
I did, my phone was temporary bricked, didn't responded to any key pressing nor adb commands. After a few minutes of waiting it actually reacted to
Code:
adb reboot
a32e_ul HTC Desire
I have a32e_ul HTC 626s 5.1.1 fw 1.23.1550.3 Sense 7.0
htcdev unlocked boot loader w/ kingroot 4.8.0 w/ root checker to verify also I install purify which comes as a dlb pck with kingroot just select the option to install when it pops up and proceed to root will finish all on its on and have a display like a circle wit a number of index 68 was mine. OEM Unlocking and USB Debugging on in developer options
Help. need recovery
denix123 said:
Help. need recovery
Click to expand...
Click to collapse
try this
Yeah need a stock recovery as well. I have a Boost Mobile Desire 626s. On 5.1 I think. TWRP runs fine on it. But I'm switching to another phone. I want to return it to stock. I'd use the RUU. But the only one available is for just Sprint. It works fine with the phone, but then it will lose the Boost Mobile boot animation. Want to avoid that.
I tried pulling the recovery_signed.img from the RUU and flashing just that. But get red triangle of death when I try to boot recovery mode.
The other stock recovery I found around here also results in red triangle of death. Currently stuck on TWRP and as a result who ever gets this phone after me won't be able to install future OTA updates. Kinda of a problem.
The phone model as shown in the download mode menu is "htc_a32ewhl"
With "OS-1.24.651.2" and date of "Nov 6 2015, 18:12:10(650321)"
I tried to flash that recovery_signed.img and I get ant error in cmd and don't know how to fix it, maybe someone can help, because I need working recovery for updating to marshmallow:
Code:
target reported max download size of 16773120 bytes
Invalid sparse file format at header magi
I need stock recovery too, maybe someone can share :/
Waizeris said:
I tried to flash that recovery_signed.img and I get ant error in cmd and don't know how to fix it, maybe someone can help, because I need working recovery for updating to marshmallow:
I need stock recovery too, maybe someone can share :/
Click to expand...
Click to collapse
Whats your carrier?
GotHeart said:
Whats your carrier?
Click to expand...
Click to collapse
I'm from Europe, my version is a32_ul
Waizeris said:
I'm from Europe, my version is a32_ul
Click to expand...
Click to collapse
By carrier i mean service provider.AT&T Tmobile those are service providers.
GotHeart said:
By carrier i mean service provider.AT&T Tmobile those are service providers.
Click to expand...
Click to collapse
Yes, I know it, but I'm from Lithuania, there are no verizon or others, like in other countries, we have other providers, I bought my phone in Tele2 service provider shop, so I don't know :/
Waizeris said:
Yes, I know it, but I'm from Lithuania, there are no verizon or others, like in other countries, we have other providers, I bought my phone in Tele2 service provider shop, so I don't know :/
Click to expand...
Click to collapse
Are you s off or s on?and what does it say in your bootloader?unlocked?and also,what is the error you got?
GotHeart said:
Are you s off or s on?and what does it say in your bootloader?unlocked?and also,what is the error you got?
Click to expand...
Click to collapse
My bootloader is unlocked, it is s-on. I don't get any error, I just can't enter to recovery mode, I think I flashed the wrong one and now it's corrupted. When I click on recovery, I just get back to HBOOT menu and can't enter to recovery. When updating the phone, the same, because phone can enter to recovery. When I click 'install now' it reboots and gets into fastboot, because can't access to recovery.
When I try to flash recovery_signed.img which uploaded one guy in this thread I get error in fastboot:
Code:
target reported max download size of 16773120 bytes
Invalid sparse file format at header magi
Waizeris said:
My bootloader is unlocked, it is s-on. I don't get any error, I just can't enter to recovery mode, I think I flashed the wrong one and now it's corrupted. When I click on recovery, I just get back to HBOOT menu and can't enter to recovery. When updating the phone, the same, because phone can enter to recovery. When I click 'install now' it reboots and gets into fastboot, because can't access to recovery.
When I try to flash recovery_signed.img which uploaded one guy in this thread I get error in fastboot:
Click to expand...
Click to collapse
Okay you didnt wipe anything did you?
If you did not your OS is still intact.
Flash this its TWRP recovery for our 626s.
https://twrp.me/devices/htcdesire626s.html
Go to fastboot and flash that like you would any other recovery. "fastboot flash recovery filename.img" where filename is the exact name of that recovery.then try rebooting your phone into the regular OS.if you dont have one,and it wont boot,i can try and offer you further instructions.do you know if your provider is GSM?
GotHeart said:
Okay you didnt wipe anything did you?
If you did not your OS is still intact.
Flash this its TWRP recovery for our 626s.
https://twrp.me/devices/htcdesire626s.html
Go to fastboot and flash that like you would any other recovery. "fastboot flash recovery filename.img" where filename is the exact name of that recovery.then try rebooting your phone into the regular OS.if you dont have one,and it wont boot,i can try and offer you further instructions.do you know if your provider is GSM?
Click to expand...
Click to collapse
Problem is that, like I said, my phone is not 626s, it is 626. I didn't wipe my os, I just flashed recovery. Yes, it is GSM provider
ive a full HTC stock recovery for HTC Desire 626 (no letters after 626) and it's around 1.99 GB. I got this file from XTC2Clip site when i had to buy one to reset my soft bricked phone.
It is currently uploading to Mega.nz due to the size. Once it's uploaded i will post the link to it.
in the mean while you can check to see if this is the right file for you.
the file name is as follows:-
0PKXIMG_A32[email protected]51007C_19.05_018_F_release_459321_signed_2_4
Update: the file is on page 3
vampman05 said:
ive a full HTC stock recovery for HTC Desire 626 (no letters after 626) and it's around 1.99 GB. I got this file from XTC2Clip site when i had to buy one to reset my soft bricked phone.
It is currently uploading to Mega.nz due to the size. Once it's uploaded i will post the link to it.
in the mean while you can check to see if this is the right file for you.
the file name is as follows:-
0PKXIMG_A32[email protected]51007C_19.05_018_F_release_459321_signed_2_4
Click to expand...
Click to collapse
Thank you very much, I will check it when you finish upload it, I hope it will work, thank you for help, I appreciate it. It's exactly what I need I think, because my version is the same
TWRP from TWRP Builder builded for Nokia 7 Plus....
I still don't know if working (as i write in another thread), so that it does not fit, i write separate thread about it...
Small story:
I unpacked B2N-132E-0-00WW-B07.nb0 using nbd tools, although is not complete unpacked, "B2N-0-132G-00WW-boot.img" is here...
Unpack using unmkbootimg and get kernel(zImage) and ramdisk(ramdisk.cpio.gz)...
In unpacked ramdisk is binary "recovery", "init.recovery.qcom.rc" and "recovery.fstab" which is used/imported by default "init.rc"...
Then i think this is recovery, using TWRP Builder APK installed on N7+ i upload this image...
After some days i receive message that TWRP for Nokia 7 Plus is builded OK
Of course flashing this need Unlocked bootloader, then all who need it, PLEASE do participate in petition about Unlocking bootloader:
https://forum.xda-developers.com/nokia-7-plus/how-to/petition-possibility-to-unlock-t3788953
(after write comment, please also click too on "Do you have this question as well?")
Download: TWRP_onyx_00ww-08051830.img
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Ranpe said:
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Click to expand...
Click to collapse
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
k3dar7 said:
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
Click to expand...
Click to collapse
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
How did you get it open? Bootloader
DroiDMester said:
How did you get it open? Bootloader
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930/
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
k3dar7 said:
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
Click to expand...
Click to collapse
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Ranpe said:
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Click to expand...
Click to collapse
strange, i not see it in complete, queue, running or rejected don't show after upload you some error like "for this device is already builded"? i don't know if is posible rebuild for same device model from another device with another/newer boot.img...
I thought too about NTool, but i not find any seller od setool2 credit with small amount of credit (<=10), only 30 and for me message no answer... also authot of NTool write me only "not help you"... then try wait what Nokia do with many question about posibility of unlocking bootloader officialy...
try to get stock recovery img, porting should be easier.
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
as i say in #0 TWRP is builded from srock recovery from 8.0 NB0 for N7p, i think problem is that N7p not use separate recovery but is inside normal boot, then need some magic to switch to recovery part of this "hybrid" boot, and because N7p need to recovery via powering cable and hold VolUp+Power then i think is same need with booting TWRP from #0, but who know if this is possible with not flashed booting via fastboot...
edit: anyway if my thoughts are true, then with hybrid boot+recovery flashed to device, is really need twrp based on exact boot image for current rootfs on device... (as Rampe too say if is possible evoce recovery from image booted via fastboot without flashing, then is not need exact version...
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
The recovery is in the boot.img, and we have the images already.
Ranpe said:
The recovery is in the boot.img, and we have the images already.
Click to expand...
Click to collapse
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
Not 100% sure of it, but unfortunately it may be so.
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
if changed kernel version/config (or binary, script, key in boot.img) then yes... if update use same files in boot.img as previous then no...
if i look at version in Settings/About for 8.1 v2.13 and 8.1 v2.22 then kernel version i same 4.4.78, but builded date is other (17.3. and 20.4.), not know if changes config, source etc, or is only same kernel rebuilded with full build proces again... i not have whole boot.img for 2.13 or 2.22 only for 8.0 v1.23
edit: FW for camera/touch/baseband/nothing not in boot.img (if not compile inside kernel(which i do not expect))
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
k3dar7 said:
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
Click to expand...
Click to collapse
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
dotsaredots said:
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
Click to expand...
Click to collapse
thanks for uploading, i now too have extracted 2.13 using payload_dumper.py (link from here), but for unpack payload.bin from 2.22 i think do not help any python "propertly working" because 2.22 is incremental update and this is not supported by payload_dumper.py...
btw: now i'm sure that N7p have really hybrid recovery_in_boot, what is used for any Phone that use new A/B method of updating on running system and simply switch to new update after reboot...
https://source.android.com/devices/tech/ota/ab/ab_implement
first of all you need to edit recovery.fstab in vendor partion it won`t boot because of encrypted data
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
X4, Pixel2 and other A/B devices use a bootable recovery image (fastboot boot twrp.img) and then install a .ZIP package that patches the boot.img with TWRP recovery.
There have been other issues on the various devices with encryption, with bootcontrol partition switching, and with handling of empty "B" partitions. So proceed with caution, especially with flashing roms from TWRP before you have a way to populate the B partition.