Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Good to see you here!
I am not sure if memory is locked to bootloader
I dont think so because ics changed the system partition size
We cant edit the .sin files in a .ftf
Sony included a file which contains a long key (like a long md5) which is unique
We cant fastboot boot. ..:... It is not included in the bootloader
If you need any info pm me
Sent from my LT22i using xda app-developers app
Hey Nicholtus!
Thanks for the reply!
So ICS upgrade changed partition layout ? On which model ? And upgrade preserved data or is it a global format ?
You're sure about fastboot boot ? Because it's doing something on Xperia S. Kernel doesn't boot, but something starts as device get stuck, so I was thinking that maybe I was not doing it the right way.
And system ext4, any idea ?
Regarding sin, I know about signature and that we have no way to bypass it.
Hi,
Layout is changed on the xperia s
I thought it was the system partition
If we find a way to bypass the sin header we can re partition the phone
I heard from DooMLoRD that the fastboot boot option is not included
Sent from my LT22i using xda app-developers app
letama said:
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Click to expand...
Click to collapse
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
munjeni said:
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
Click to expand...
Click to collapse
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
I should ask that someday on sony forum I guess.
Regarding the extract of ics, I solved the issue since then, the issue was an incomplete understanding of sin format. Since that time, I wrote a tool that can directly extract sin properly and Androxyde introduced similar changes in recent releases of FlashTool, so now it can be all done on PC without having to flash and dump.
I saw also your investigation regarding boot partitions, isn't the second one the one used for fotakernel ?
Just in case you want to look into this, don't bother if your bootloader is similar to Xperia S . I wanted to use it to have a second kernel for recovery, but after looking at bootloader, booting from this partition is blocked by bootloader as soon as you unlock your bootloader.
This is why I came to this, three different kernels boot with one dedicated to recovery .
letama said:
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
Click to expand...
Click to collapse
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
munjeni said:
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
Click to expand...
Click to collapse
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
Click to expand...
Click to collapse
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
munjeni said:
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
Click to expand...
Click to collapse
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
letama said:
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
Click to expand...
Click to collapse
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
K900 said:
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Click to expand...
Click to collapse
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
munjeni said:
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
Click to expand...
Click to collapse
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
letama said:
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
Click to expand...
Click to collapse
Fastboot is actually open source in AOSP.
K900 said:
Fastboot is actually open source in AOSP.
Click to expand...
Click to collapse
Yes, but I was looking for hidden/unknown oem commands, found known
Is bootloader partition locked? We can write to him by dd?
munjeni said:
Is bootloader partition locked? We can write to him by dd?
Click to expand...
Click to collapse
The bootloader is not stored on the eMMC.
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Wow. We've got an expert here.
K900 said:
The bootloader is not stored on the eMMC.
Click to expand...
Click to collapse
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
---------- Post added at 06:26 PM ---------- Previous post was at 06:26 PM ----------
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
munjeni said:
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
Click to expand...
Click to collapse
The lowest level thing is not there, and I'm pretty sure that's what blocks fotakernel.
munjeni said:
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
Click to expand...
Click to collapse
It should work now with a recent flashtool. Androxyde implemented my sin extraction method that properly extract ext4.
Sent from my LT26i using xda app-developers app
Related
T329w is customized version Of Desire X (t329e) which have to SIM card
The rom for Desire X running Perfect on my T329w except there is no Signal...
I think flash back the T329w's stock Kernal and Radio can fix it?
Has anyone can Help me?
Thanks a Lot !
link of Rom for T329w
Version 1
http://pan.baidu.com/s/122oNL
Version 2
http://pan.baidu.com/s/1oVdzO
Hi
You can downlod from here:https://hotfile.com/dl/249367403/0b72cc6/T329W.rar.html
This is decrypt stock rom for T329w without "System.img"
I can't install this,
more details: http://forum.xda-developers.com/showthread.php?t=2483223
BABAK236 said:
Hi
You can downlod from here:https://hotfile.com/dl/249367403/0b72cc6/T329W.rar.html
This is decrypt stock rom for T329w without "System.img"
Click to expand...
Click to collapse
I need the Stock Recovery for T329w as by mistake flashed Single sim recovery. I am from India and using Stock ROM with JB (version 4.1.1).
Flashing the "recovery_signed.img" inside the folder of this Download would be helpful?
Please reply.
Thanks.
arindam4u said:
I need the Stock Recovery for T329w as by mistake flashed Single sim recovery. I am from India and using Stock ROM with JB (version 4.1.1).
Flashing the "recovery_signed.img" inside the folder of this Download would be helpful?
Please reply.
Thanks.
Click to expand...
Click to collapse
I think it will
Did the same mistake..
Any help on this front will be useful
yashvchauhan said:
Did the same mistake..
Any help on this front will be useful
Click to expand...
Click to collapse
There is a dual sim rom in one of these threads, flash that and after that flash the correct stock recovery.
And next time read carefully because this forum is not for the the Desire X dual sim
GtrCraft said:
There is a dual sim rom in one of these threads, flash that and after that flash the correct stock recovery.
And next time read carefully because this forum is not for the the Desire X dual sim
Click to expand...
Click to collapse
Searched, couldn't find any dual sim roms apart from the one in this thread
EDIT - or maybe it's this one? it's compatible with dual sim http://forum.xda-developers.com/showpost.php?p=46730392&postcount=30
thanks for your help though..
This is what i plan to do :
Download and flash TWRP for t329w
Transfer http://pan.baidu.com/s/122oNL (version 1) to SD Card and the recovery_signed.img and boot_signed.img to SC Card
Reboot phone to recovery
Choose Wipe then Swipe to Factory Reset
or the best is Select Advance Wipe, tick all except sdcard then swipe to wipe
Select Install and select the version1 rom.zip then swipe to confirm flash
Wait until the installation is finished
Reboot phone to fastboot and connect it to your PC
Open command prompt, lead it to folder where you installed adb and fastboot and issue commands:
fastboot flash recovery C:\recovery_signed.img
fastboot erase cache
fastboot reboot
fastboot flash boot c:\boot_signed.img
fastboot erase cache
fastboot reboot
yashvchauhan said:
Searched, couldn't find any dual sim roms apart from the one in this thread
EDIT - or maybe it's this one? it's compatible with dual sim http://forum.xda-developers.com/showpost.php?p=46730392&postcount=30
thanks for your help though..
This is what i plan to do :
Download and flash TWRP for t329w
Transfer http://pan.baidu.com/s/122oNL (version 1) to SD Card and the recovery_signed.img and boot_signed.img to SC Card
Reboot phone to recovery
Choose Wipe then Swipe to Factory Reset
or the best is Select Advance Wipe, tick all except sdcard then swipe to wipe
Select Install and select the version1 rom.zip then swipe to confirm flash
Wait until the installation is finished
Reboot phone to fastboot and connect it to your PC
Open command prompt, lead it to folder where you installed adb and fastboot and issue commands:
fastboot flash recovery C:\recovery_signed.img
fastboot erase cache
fastboot reboot
fastboot flash boot c:\boot_signed.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Perfect steps, if those two roms don't work then try this: http://sourceforge.net/projects/others/files/DX/Dual SIM/T329w_2.12.1402.1.zip/download
(That was the one I meant)
GtrCraft said:
Perfect steps, if those two roms don't work then try this: http://sourceforge.net/projects/others/files/DX/Dual SIM/T329w_2.12.1402.1.zip/download
(That was the one I meant)
Click to expand...
Click to collapse
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
---------- Post added at 06:57 AM ---------- Previous post was at 06:21 AM ----------
There's a guy on FB who had a similar problem. He said he flashed a "brushed" ROM from a chinese forum (i got the links), well if you translate it means a modified ROM for the dual sim, right? He also said he was missing the RUU. Any help here would be appreciated.. Thanks a lot!
Heres what he said
"i used a brushed rom and installed through twrp recovery bro . check the link i sent u can translate it and find everything . i couldnt find ruu file"
yashvchauhan said:
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
Click to expand...
Click to collapse
After restoring Nandroid, just fastboot flash the boot_signed.img and reboot and see whether it boot. It should work if the custom recovery is working well for your device. No need to fastboot flash recovery_signed.img first. Just boot and see whether it works. If it works then only you fastboot flash the recovery_signed.img if you want to.
Don't worry about other images as you can't flash those on a S-On device.
ckpv5 said:
After restoring Nandroid, just fastboot flash the boot_signed.img and reboot and see whether it boot. It should work if the custom recovery is working well for your device. No need to fastboot flash recovery_signed.img first. Just boot and see whether it works. If it works then only you fastboot flash the recovery_signed.img if you want to.
Don't worry about other images as you can't flash those on a S-On device.
Click to expand...
Click to collapse
HELP!! I flashed the boot.img and now the phone doesn't boot. Shows white screen then blackout.
adb doesn't detect it
help!!
yashvchauhan said:
HELP!! I flashed the boot.img and now the phone doesn't boot. Shows white screen then blackout.
adb doesn't detect it
help!!
Click to expand...
Click to collapse
Inside your nandroid backup there is a file boot.emmc.win, this is your stock boot.img
So fastboot flash this one with command
fastboot flash boot boot.emmc.win
ckpv5 said:
Inside your nandroid backup there is a file boot.emmc.win, this is your stock boot.img
So fastboot flash this one with command
fastboot flash boot boot.emmc.win
Click to expand...
Click to collapse
shows Error : Cannot open boot.emmc.win
Is it because my nandroid is on external sd? I'm using nexus prime as the recovery
yashvchauhan said:
shows Error : Cannot open boot.emmc.win
Is it because my nandroid is on external sd? I'm using nexus prime as the recovery
Click to expand...
Click to collapse
What do you mean shows Error : Cannot open boot.emmc.win ? boot.emmc.win is created by a TWRP recovery only. If there is one you don't have to "open" it, just copy it to your fastboot folder
Now you mentioned you use nexus prime as the recovery do you mean you use NexusRecovery ? Can you list here the file names inside the nandroid backup ? I don't think you have boot.emmc.win in NexusRecovery
ckpv5 said:
What do you mean shows Error : Cannot open boot.emmc.win ? boot.emmc.win is created by a TWRP recovery only. If there is one you don't have to "open" it, just copy it to your fastboot folder
Now you mentioned you use nexus prime as the recovery do you mean you use NexusRecovery ? Can you list here the file names inside the nandroid backup ? I don't think you have boot.emmc.win in NexusRecovery
Click to expand...
Click to collapse
Hmm, i went to Nandroid restore > Advanced restore > Restore boot
doesn't boot.
tried restoring the whole backup, doesn't boot.
even a wipe data/factory reset doesn't make it boot!
Will taking it to an HTC centre help? (I'm ready to pay some amt of money.)
Oh no... you don't know what fastboot flash means ? It is not using the recovery to restore boot. You need to copy the boot.img to your PC where you have all your fastboot files in a folder.
Try again this way as I don't have my PC with me. Replying to you with someone else PC.
In my ROM threads, you will see Boot.img_Installer_RCx.x.zip in post #1. Download any of them then do the following
1. Download theBoot.img_Installer_RCx.x.zip and extract it on your PC desktop
2. Reboot your DX to bootloader and connect to your PC (you should see the word "fastboot usb" in red color on the bootloader)
3. Open the Boot.img_Installer_RCx.x folder that you extracted, you should see a batch file Install Boot.img.bat there
4. Replace the boot.img with your boot.img (don't use the one that already in the folder). Try the boot_signed.img that you have, rename it to boot.img
5. Run that Install Boot.img.bat and when it stop just press any key to exit
6. Reboot
And yes, taking it to HTC centre will help but of course you need to pay them
ckpv5 said:
Oh no... you don't know what fastboot flash means ? It is not using the recovery to restore boot. You need to copy the boot.img to your PC where you have all your fastboot files in a folder.
Try again this way as I don't have my PC with me. Replying to you with someone else PC.
In my ROM threads, you will see Boot.img_Installer_RCx.x.zip in post #1. Download any of them then do the following
1. Download theBoot.img_Installer_RCx.x.zip and extract it on your PC desktop
2. Reboot your DX to bootloader and connect to your PC (you should see the word "fastboot usb" in red color on the bootloader)
3. Open the Boot.img_Installer_RCx.x folder that you extracted, you should see a batch file Install Boot.img.bat there
4. Replace the boot.img with your boot.img (don't use the one that already in the folder). Try the boot_signed.img that you have, rename it to boot.img
5. Run that Install Boot.img.bat and when it stop just press any key to exit
6. Reboot
And yes, taking it to HTC centre will help but of course you need to pay them
Click to expand...
Click to collapse
Hmm, I will try that. Guess I will have to take it anyway coz of the SIM card issue.
Thanks a lot man. You've been a great help. Appreciate every bit of it.
yashvchauhan said:
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
---------- Post added at 06:57 AM ---------- Previous post was at 06:21 AM ----------
There's a guy on FB who had a similar problem. He said he flashed a "brushed" ROM from a chinese forum (i got the links), well if you translate it means a modified ROM for the dual sim, right? He also said he was missing the RUU. Any help here would be appreciated.. Thanks a lot!
Heres what he said
"i used a brushed rom and installed through twrp recovery bro . check the link i sent u can translate it and find everything . i couldnt find ruu file"
Click to expand...
Click to collapse
don't flash the radio hboot and other files than boot and recovery
[
yashvchauhan said:
Hmm, I will try that. Guess I will have to take it anyway coz of the SIM card issue.
Thanks a lot man. You've been a great help. Appreciate every bit of it.
Click to expand...
Click to collapse
Ohh, I just read it properly. I know what fastboot flash means. Using Android SDK > Platform tools > Shift+rightclick > open as command prompt > fastboot flash boot boot_signed.img
I've already done it. This boot_signed.img in this thread seems weird.
After installing the custom ROM, restoring my nandroid backup, my phone was booting, but without the sim being recognized.
So I fastboot flashed the above (second post of this thread) boot_signed.img from c:\
But THAT boot_signed.img led to my phone being stuck in a bootloop > white start screen > turns black > try switching it on again > same thing
Hoped I could restore the nandroid boot using recovery advanced restore, but didn't work.
Will try fastboot flashing the MIUI boot.img (coz that's what was working initially, though without a sim, and the one in this thread's second post doesn't have a source), atleast that should get my phone booting. And will try searching for the boot of my nexus recovery backup, coz that will be the stock boot.img.
My last thing before I go to HTC .
---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------
GtrCraft said:
don't flash the radio hboot and other files than boot and recovery
Click to expand...
Click to collapse
I only flashed boot and recovery, not the others
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
tomolewis said:
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
Click to expand...
Click to collapse
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
chronic8000 said:
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
Click to expand...
Click to collapse
look this
http://www.forum-generationmobiles.net/f447-one-touch-idol-s
Any news on this?
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
chronic8000 said:
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
Click to expand...
Click to collapse
reflash
pmarkov said:
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
Click to expand...
Click to collapse
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
gabcs said:
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
Click to expand...
Click to collapse
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Root Alcatel
Hello everyone, Esque quelqun could tell me when will esqu'on rooter The alcatel one touch idol 2 mini S android 4.3 please
zlamar said:
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Click to expand...
Click to collapse
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
gabcs said:
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
Click to expand...
Click to collapse
pmarkov said:
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
Click to expand...
Click to collapse
Try this: shared.com/7dwx96a1yy?s=l
This is from the french forum - I already tried exactly this image with no success.
gabcs said:
Try this: shared.com/7dwx96a1yy?s=l
Click to expand...
Click to collapse
pmarkov said:
This is from the french forum - I already tried exactly this image with no success.
Click to expand...
Click to collapse
your phone is 6034 or 6035? i tried on 2 phones (6034r) and the custpack is work. one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
gabcs said:
one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
Click to expand...
Click to collapse
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
zlamar said:
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
Click to expand...
Click to collapse
Sorry, but my english is bad. But yeah, i know, i spent 3 days (0-24) to fix this phone. For me the reflash custpack, boot and system img worked from my first post. From mediafire folder need just the 2 roms. the first 70mb is only the system. The orange rom i think the full rom. Yes, every two are cwm flashable. Try to flash the img-s in bootloader mode after flash the 70mb rom with cwm. If dont work make a factory reset with cwm and flash the 233mb orange rom. This phone's software like a nightmare. No source code, everything is different like in other phones and nobody knows the different between the 6034 and 6035. I better like my OT-991 with MTK soc...
@gabcs
Unfortunatelly, after no success in searching for solution (couldn't find the ROM), two weeks ago, I gave up and sent my phone to service center and I hope that they will resolve the problem. Big and frustrating issue was that I couldn't get to bootloader any more, so the phone couldn't recieve adb commands, only thing that worked was CWM...
Service center will resolve that for 20 euros, and I will resolve my nerves
Anyway, thank you for your time and your help.
@zlamar,
what happened with your phone? Did you managed to have it repaired/restored? My phone is still bricked and It seems the problem is to find the appropriate custpack image as the french versions don't work for other countries.
Still nothing.... Service center where I gave it for repair isn't authorised and they didn't resolve the issue.
Does anybody have a full CWM backup image, and is willing to share it and upload it somewhere?
It has nothing to do with authorization, they just don't have alcatel service access.
There is special alcatel service flasher, that works online, and is intended for Qualcomm platform.
I played with it, and re-flashed my 6016x (MSM8210 - Qualcomm Snapdragon 200).
If you were somewhere closer, I would repair it for 20€ very fast and effiecent
@pmarkov ... I have original files but they are useless, because no any flasher to use them.
b.r.
ALex
Hi Alex,
Thanks for the clarification. Obviously this magic flashing tool is only internaly available for authorized service providers. Today I contacted the official local partner of Alcatel and they were positive they can handle the reflashing for approx. 20 EUR. Let's hope they really will fix it.
BR
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
DooMLoRD said:
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system [UPLOADING]
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
scrubber said:
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
Click to expand...
Click to collapse
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
DooMLoRD said:
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
Click to expand...
Click to collapse
Ok. Will arrange topic
scrubber said:
Ok. Will arrange topic
Click to expand...
Click to collapse
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
No problem, any source and can parts
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
We can wait
joluke said:
We can wait
Click to expand...
Click to collapse
scrubber said:
No problem, any source and can parts
Click to expand...
Click to collapse
done
https://mega.co.nz/#!4RNx0Jaa!trTgJIXt8bB9R8LW6z3IVejSRV0MfqNvviD769UUsDo
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
pudgewack said:
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
Click to expand...
Click to collapse
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
ekrunch said:
Forgive the long post
Click to expand...
Click to collapse
Nice, well explained post.
ekrunch said:
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Click to expand...
Click to collapse
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
ddslee said:
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Click to expand...
Click to collapse
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
ekrunch said:
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
Click to expand...
Click to collapse
thanks for creating it i was lazy to write all this
DooMLoRD said:
....
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
...
Click to expand...
Click to collapse
Preview comes out ok as the hardware does initialize. The issue is, from what I have seen and other who may have corroborated this, is the AF on the camera. You see, photosphere actually works well, just not the regular camera. Someone else mentioned that apps using infinity focus work as well.
My guess is that something in 4.4.3 and 4.4.4 (maybe in the kernel?) is looking for the missing DRM keys from devices with unlocked BL. Several people have already stated that they have no issues with their cameras, with the only difference being the locked bootloader in their devices. Considering that Sony had done something similar with the Z1 last year, I would not be surprised if it was the case here as well. Not sure why this would be the case for a GPE unit as it has no proprietary software (other than X-Reality)...
As I said, nothing but a guess albeit it does make sense (to me anyways).
Finally!!
Finally got my GPE to update using ekrunches excellent post..it took a little fiddling, (WIPE!! REALLY!!) but everything else went quite smoothly. I did find that fastboot -w didn't format partitions on cache and data and ended up in stock recovery to do a full wipe, after which things worked perfectly. Before that it was bootlooping on me. Didn't fix the camera though. I may leave this sucker mostly stock until someone fixes the camera...and on that note-I unlocked my bootloader immediately on getting the phone, before any updates ran. I've been considering the idea that if you unlocked before 4.4.2, that might be what's messing the camera up. I don't have any evidence for this though, it's just a guess.
DooMLoRD said:
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
Click to expand...
Click to collapse
hahahaha I did. But it's the same for the boot and FOTAKernel images. What kept throwing me was one working while the other didn't but they were both the same type of file. How nice of Sony to do this... *cough cough*
DooMLoRD said:
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Click to expand...
Click to collapse
So is there a better way to flash that boot image or is this it?
DooMLoRD said:
thanks for creating it i was lazy to write all this
Click to expand...
Click to collapse
You're quite welcome. Thank you for all of the dumps, kernels, write ups, etc. It is much appreciated. I've been leeching information from this forum for years with no contribution other than some donations so I'm glad to help out. I was beating my head up against the wall when I wrote that first post as it was driving me crazy that I couldn't flash that boot image. I've been spoiled by Nexus devices.
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Pallavgarg10 said:
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Click to expand...
Click to collapse
Depends what you are trying to achieve?
Fully update your new GPe ZU?
From 4.4.2 to 4.4.4?
Already rooted or not, if not I would just flash the OTAs
I just want to update to 4.4.4 with as little modification as possible
Hi,
I have the Z5C with the latest stock firmware.
I wanted to do a little change to the /system/etc/hosts file. I tried to be smart (and failed). I did not want to flash anything so I only booted into TWRP, changed the file in terminal and rebooted.
Unfortunately after doing so I can neither boot to recovery or to the system itself. Fastboot works fine though. If I messed up the /etc/hosts then the recovery would still work fine - this rules out this option.
So after that I tried
rebooting
fastboot boot recovery.img
fastboot flash recovery recovery.img
...
If I unplug the cable in fastboot the phone just dies. If I turn it on it gets stuck on the Sony logo.
I did not expect that just booting to a recovery without actually flashing it could break anything Any idea please?
To even boot TWRP you have to have an unlocked bootloader. You may have presumed that by unlocking the bootloader that the integrity of the other partitions are no longer checked; however, the /system partition is in fact still protected by the Android "dm-verity" feature (https://source.android.com/security/verifiedboot/) even when bootloader is unlocked. So by mounting /system as read/write on TWRP and modifying the hosts file, you have changed the checksum of the /system partition.
You have two options:
Flash a modified kernel to the boot partition that disables dm-verity. Then you should be able to get the phone to boot with your modified /system partition. (I recommend this utility: https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605 -- use this even if you don't want to root the phone: it will ask you individually what changes you want it to make to the kernel, and you can choose to *just* disable dm-verity if that's the only change you want to have made.)
Download the FTF for your firmware, and re-flash *just* the system partition with Flashtool in order to undo the change you made (Flashtool will allow you to selectively flash only certain partitions from a given firmware).
-- Nathan
Awesome! Makes sense! Thanks a lot.
After your reply it somehow (I do not know why) allowed me to boot to recovery. Therefore I reverted the change. I should have thought that it is going to checksum to verify the system integrity.
letalvoj said:
Awesome! Makes sense! Thanks a lot.
After your reply it somehow (I do not know why) allowed me to boot to recovery. Therefore I reverted the change. I should have thought that it is going to checksum to verify the system integrity.
Click to expand...
Click to collapse
You mean you simply edited the 'hosts' file and put the contents back to the way that they were? Honestly, if so, I'm surprised that worked...as I understand it, dm-verity happens on a block-level basis, not a file-level one, so even restoring the contents of particular files would not cause the checksum to go back to matching what the system is expecting (file contents now stored at different blocks/LBAs, file timestamps changed, etc.), which is why I thought flashing the original stock contents of the system partition would be necessary. In any case, glad to hear you are back in business.
-- Nathan
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205