Related
ok.. i have done some googling on this error but the only results were japanese.
i have 2 identical phones, one is bricked but can get into fastboot, the other is fully working and has root.
i have used the dd command to copy the boot, recovery and system images.
when i went to flash them system.img flashed fine, but boot.img and recovery.img are sent ok but fail on flashing with this error: "remote: size too large" and wont flash, but if i execute :"fastboot boot boot.img" the phone will boot into android.
i have tried the android control fastboot protocol and adb one with no luck.
the phone is a huawei ascend p1 lte (U9202l-1)
bump: anyone know how to fix this
help anyone? could someone at least say if there is no way to fix this
nitros12 said:
help anyone? could someone at least say if there is no way to fix this
Click to expand...
Click to collapse
Hi there,
First, could you tell me the name of the phone, plus your provider?
its a huawei ascend p1 lte (model number: U9202l-1) provided by t-mobile (or ee)
nitros12 said:
its a huawei ascend p1 lte (model number: U9202l-1) provided by t-mobile (or ee)
Click to expand...
Click to collapse
Okay,
My recommendation, nitros, would be to download the Android SDK, and try to flash the ROM yourself.
I will attach an XML file, that is the general syntax followed when flashing a device.
If you are running windows, download the android sdk, and open up command prompt as an administrator, and input the following commands:
cd \[put file path to the android sdk here]\sdk\platform-tools
And follow the steps provided in the XML file.
Good luck!
If this fails, let me know.
PS: Only input the operations that are located between <steps interface="AP"> and </steps>.
If the command says <step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="3273A6FDFDFA35D2E5FCE4B3FBB1764F" />, then you type in "fastboot sbl1 sbl1.mbn".
If the command says <step operation="reboot-bootloader" /> then you type in "fastboot reboot-bootloader".
If the command says <step operation="erase" partition="modemst2" />, then you type in "fastboot erase modemst2".
i have the sdk but now how do i get hold of the rom.
do i have to make it from a dump
nitros12 said:
i have the sdk but now how do i get hold of the rom.
do i have to make it from a dump
Click to expand...
Click to collapse
I don't know the solution, but if you have a dump, please tell me, because i have a bricked p1 lte too and i would like to unbrick it!
Please someone must help!
here
entonjackson said:
I don't know the solution, but if you have a dump, please tell me, because i have a bricked p1 lte too and i would like to unbrick it!
Please someone must help!
Click to expand...
Click to collapse
here: i have the boot, system and recovery.img
https://docs.google.com/file/d/0BzsA17IjC5k2aVpncUoxaGZSczg/edit?usp=sharing
https://docs.google.com/file/d/0BzsA17IjC5k2YzZWemRjZk9leEk/edit?usp=sharing
nitros12 said:
here: i have the boot, system and recovery.img
https://docs.google.com/file/d/0BzsA17IjC5k2aVpncUoxaGZSczg/edit?usp=sharing
https://docs.google.com/file/d/0BzsA17IjC5k2YzZWemRjZk9leEk/edit?usp=sharing
Click to expand...
Click to collapse
and how do i need to flash this, please tell me!!
heres what i did to get it working: get android control, start cmd in its directory, boot into fastboot (power and volume down) and type: fadtboot boot (where boot. img is located)/boot.img, if it boots good if not restart back to fastboot and type: fadtboot flash system.img and then boot boot.img.
when it boots, open android control and co to the flashing tab, flash boot.img first then recovery, if it works great.
the reason you need to use android control is because it runs a few more commands that stop it giving the error i made this thread for.
Sent from my U9202L-1 using xda app-developers app
nitros12 said:
heres what i did to get it working: get android control, start cmd in its directory, boot into fastboot (power and volume down) and type: fadtboot boot (where boot. img is located)/boot.img, if it boots good if not restart back to fastboot and type: fadtboot flash system.img and then boot boot.img.
when it boots, open android control and co to the flashing tab, flash boot.img first then recovery, if it works great.
the reason you need to use android control is because it runs a few more commands that stop it giving the error i made this thread for.
Sent from my U9202L-1 using xda app-developers app
Click to expand...
Click to collapse
You posted the boot.img and recovery.img, i also need the system.img, please
its being uploaded now, system. img is 67MB
but try getting it to work without system.img 1st
Sent from my U9202L-1 using xda app-developers app
nitros12 said:
its being uploaded now, system. img is 67MB
but try getting it to work without system.img 1st
Sent from my U9202L-1 using xda app-developers app
Click to expand...
Click to collapse
Ok, please post the link when it's finished. You are awesome dude! i hope i get this phone running again!
have to stop uploading now, end of my "pc time" will start again tomorrow
i have to do some homework and the computer is not allowed to be on when nobody is using it.
Sent from my U9202L-1 using xda app-developers app
nitros12 said:
have to stop uploading now, end of my "pc time" will start again tomorrow
i have to do some homework and the computer is not allowed to be on when nobody is using it.
Sent from my U9202L-1 using xda app-developers app
Click to expand...
Click to collapse
OK, i will wait until tomorrow. But give me a promise to upload the file. You are my only hope!
Please!
will continue tommorrow
Sent from my U9202L-1 using xda app-developers app
I have a bad feeling that it won't work.
Because I already tried
Code:
fastboot flash boot boot.img
and
Code:
fastboot flash recovery recovery.img
with your two files. and both gave this error:
FAILED (remote: Download size too large)
Click to expand...
Click to collapse
Are you sure this will work?
yea
entonjackson said:
I have a bad feeling that it won't work.
Because I already tried
Code:
fastboot flash boot boot.img
and
Code:
fastboot flash recovery recovery.img
with your two files. and both gave this error:
Are you sure this will work?
Click to expand...
Click to collapse
yes, it did the same thing to me: first boot into boot.img with: [/CODE]fastboot boot boot.img[/CODE]
then use android control to flash boot.img, android control does some other commands that let it work
nitros12 said:
yes, it did the same thing to me: first boot into boot.img with: [/CODE]fastboot boot boot.img[/CODE]
then use android control to flash boot.img, android control does some other commands that let it work
Click to expand...
Click to collapse
Hey! Thanks for the info.
I will try it, when I'm back from work.
Are you already uploading? I really need the system.img
after up rom miui 3.5.17 http://forum.xda-developers.com/showthread.php?t=2213168
my atrix can't root , can't enter recover CWM
I tryed flash by RSDlite but fall : failed flashing process. Unable to retrieve interface
help me plz .
voz111 said:
after up rom miui 3.5.17 http://forum.xda-developers.com/showthread.php?t=2213168
my atrix can't root , can't enter recover CWM
I tryed flash by RSDlite but fall : failed flashing process. Unable to retrieve interface
help me plz .
Click to expand...
Click to collapse
are you using the correct sbf file for your carrier? are you using the sbf file that matches the stock version you had prior to unlocking the bootloader?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
are you using the correct sbf file for your carrier? are you using the sbf file that matches the stock version you had prior to unlocking the bootloader?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
yes correct, i was used it before
voz111 said:
yes correct, i was used it before
Click to expand...
Click to collapse
what about drivers? are they up to date? do you have rsd up to date as well?
Sent from my MB860 using xda app-developers app
forrigmats
palmbeach05 said:
what about drivers? are they up to date? do you have rsd up to date as well?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
5.6 and 5.7 rsd
before have prolem i flash but not fall
ofomospmany
Failed flashing process. Unable to retrieve interface handle. (0x7027). .
voz111 said:
Failed flashing process. Unable to retrieve interface handle. (0x7027). .
Click to expand...
Click to collapse
i just copied and pasted your last post and ran a search on it. here's a solution
Solved !
1. Copy Radio image (baseband) to the folder where located fastboot. 2. Power on phone and select fastboot 3. execute: fastboot flash radio bp.img, Where bp.img baseband image files 4. execute: fastboot reboot 5. Phone automatically boot on the android recovery mode 6. Wipe userdata/cache 7. Reload in RSD mode 8. on the RSD lite browse appropriate .sbf file and puch Start
Thats all.
This makes sense, since there was a radio update since the sbf files have been out
http://www.mediafire.com/?q83792uk2f895 for radios
Sent from my MB860 using xda app-developers app
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Flash stock rom lenovo k5
try turning off your internet connection and flash sorry for my inglis I'm using google translate
Nox.BG said:
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Click to expand...
Click to collapse
I'm stuck on the "fire hose" file. QFIL seems to not detected the phone.
Did you managed to solve the problem?
Lenovo K5 Pro ROM
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
ShmuelCohen said:
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Did you get any solution, I have the same problem.
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
help me what is the correct file to download to flash android 10 on lenovo k5 pro. Gapps and custom rom please help. Im stock the google pixel logo boot screen for almost an hour.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
shisho585 said:
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
Click to expand...
Click to collapse
.
iugleafar said:
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
Click to expand...
Click to collapse
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
thank you very much this have save me a lot of times.
my windows computer have problem with fastboot driver. i installed realme adb-fastboot driver again and again but it doesnt work, device manager still have ''question mark'' android driver, maybe windows need to be reinstall or something... i use the same pc to unlock bootloader before,
i unpack the ozip on raspbian (using raspberry pi 3 with microsd) , fastboot flash realme x 3 that i messed up before and now it work.
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
ash1337x said:
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
Click to expand...
Click to collapse
ignore twrp thing and u didn't follow everything as u have twrp u should install stock recovery
everything is cool but i have multiple super imgs what do i do?
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
Send me stock recovery please
prabal_2004 said:
everything is cool but i have multiple super imgs what do i do?
Click to expand...
Click to collapse
Yes, 4 or 5 super img files how to flash
4 or more super img files, with defrent name
Sajeevkaif said:
4 or more super img files, with defrent name
Click to expand...
Click to collapse
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
for me, i have 1 super.0 file with 2.86gb
1 super.1 file 1.95gb
and 12 super.2 files ranging 800mb to 1.8gb
what should i get for the super.img?
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
CloudChase said:
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
Click to expand...
Click to collapse
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
what should i do? i need to fix my phone
CloudChase said:
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
Click to expand...
Click to collapse
CloudChase said:
what should i do? i need to fix my phone
Click to expand...
Click to collapse
I referred to the super image size, it's unlikely that the image has just this size, anyway it doesn't hurt to try it, flash some of them and see, you can try using fastboot too.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
No, all of threm have Difrent name and size (more than a gb file)
Sajeevkaif said:
No, all of threm have Difrent name and size (more than a gb file)
Click to expand...
Click to collapse
Did you try flashing one of them?
SubwayChamp said:
Did you try flashing one of them?
Click to expand...
Click to collapse
No,
There is a tool to merge Super Image if they are split into multiple files.
Follow this tutorial to merge it. Find the exact tool from Google search and ensure it has the orange logo as seen in the video.
my bad I didn't open xda for a long time as this device doesn't have much support on xda
yea only a10 has 1 super img other ones have multiple super imgs
if ur in still in stock u can use partition backup app(needs root) from playstore to backup required img files
I'll try to upload separate img files from a11 and a12 backed up here soon
So I have the Canadian G8X and erased all portions from it and am having one hell of a time fixing it. I have tried to follow the guides on here about how to unbrick and nothing works for me. My pc crashed so I have no backups of any firmware just a phone with edl mode so us there anyone that can help me get it back to working state? I have tried extracting the files from KDZ but it fails every time trying to extract the DZ file i keep getting errors message "unicode decode error utf-8 invalid start byte" i have tried downloading shared partition files from xda threads but they fail when trying to flash them using Qfil with Firehose sm-8150 what do you need to know? What how do I fix this? Its been over 2 months ice been trying to get it working
Really? Nobody can help me? I don't know what I'm doing wrong
Try this to extract the firmware,and use Qfil to write boot and recovery back to the device.That should get you in to download mode to flash the kdz of choice.
surgemanx said:
Try this to extract the firmware,and use Qfil to write boot and recovery back to the device.That should get you in to download mode to flash the kdz of choice.
Click to expand...
Click to collapse
Thank you I'm trying it
surgemanx said:
Try this to extract the firmware,and use Qfil to write boot and recovery back to the device.That should get you in to download mode to flash the kdz of choice.
Click to expand...
Click to collapse
i get this error every time
Traceback (most recent call last):
File "undz.py", line 1068, in <module>
File "undz.py", line 1064, in main
File "undz.py", line 838, in saveHeader
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position 128: invalid continuation byte
[10108] Failed to execute script undz
Ratty696 said:
i get this error every time
Traceback (most recent call last):
File "undz.py", line 1068, in <module>
File "undz.py", line 1064, in main
File "undz.py", line 838, in saveHeader
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position 128: invalid continuation byte
[10108] Failed to execute script undz
Click to expand...
Click to collapse
Here's boot_a and boot_b from the G85030b QM firmware.Try writing these with Qfil and see if it will boot in to download mode.
Edit:Try this firehose with the Qfil backups you have and see if it will write.Worth a shot?!?!