Hi all, i am a noobie trying to get as much out of my r800i as possible so obvious I tried to go the flashing route. I have encountered the follow problems so my play is soft bricked and I can't seem to get out of it. I spent the last 6 hours reading this forum trying to learn as much as I but it's just too vast. Here I go:
windows 10 64bit with driver siginature verification off
using flashtool 0.9.20.0
I tried using flashtool 64bit (flash mode) to flash various ftf to r800i (so far I have tried DoomKernelV14(GB).ftf/ExtremeV03-720p[GB].ftf/egacyXperia-CM7[GB].ftf/LupusV12-720p[GB].ftf, all of them gave me the error message like below:
Code:
- ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";\00
I then decided to try the fastboot in the commendline route, the steps are as following:
flashboot flash boot lupus.zeus.gingerbreadv12-full.img was successful
fashboot boot ClockWorkMod5.0.2.8.img (because I read in the forum that r800i doesn't have recovery partition so I can't flash it, which seems to be true; when I tried to flash recovery the CWM img, the error message was that recovery partition can not found)
r800i rebooted and got in the CWM recovery successfully. I then did factory reset/wipe cache then install gin2kitkat3.3.0.zip which was successful as well.
after the previous 3 actions everything was successful (no error messages) so I felt very good about it but unfortunately after rebooting the r800i, all I got was a lupus image then 2 vibrations then screen is off.
I then did the same thing twice again to make sure I didn't miss any error message (which I didn't) but still the phone is as soft-bricked as ever.
I would really appreciate if someone can help me out of the jam because I just bought the r800i to get back to retro-gaming. thank you!
edit:
I should add that when I got the phone it was working perfectly with custom recovery (sorry I don't remember which version but I believe it's CWM) and DooMKerneL but slow (ICS rom which I didn't write down).
I would like to use gin2kitkat3.30 but after installing the gin2kitkat roms (both 3.1.0 and 3.3.0), the wifi doesn't work and I couldn't find way to "flash the wifi module" (I read it in the forum but never got detailed info), so I decided to flash the Lupus kernel, and that's where everything starts.
Try to find older version of flashtool (0.9.16 or older). That should fix your problem with flashtool
You are right, Play don't have recovery partition, only kerrnel (boot), system and data partition. But all custom kernel have integrated recovery, so when you flash kernel, you have recovery.
You are having problems with Lupus kernel because it uses different partition layout of system and data partion and it won't boot if previous kernel had stock partition layout. Doomlord kernel use stock partition so you are able too boot into ROM if you had stock kernel flashed prior Doomlord kernel. FYI, Doomlord and stock kernel have 310MB system partittion and 380 MB data partition, and Lupus kernel have 270MB system and 640MB data partition (or number close to that, i forgot exact numbers)
To be able to boot into ROM with Lupus kernel, you must erase system and data partition AFTER you flashed Lupus kernel and BEFORE you flashed any ROM from recovery.
Two ways to do it:
1. flash kernel (from flashtool or any way you can)
enter fastboot and type:
Code:
fastboot erase userdata
fastboot erase system
rebot to recovery and flash ROM
2. Flah kernel (from flashtool or any way you can)
enter recovery and use options in recovery to erase system and data partion
reboot to recovery again and flash your ROM
TL;DR version: erase system and data everytime you change kernel with different partitions , before flashing ROMS
About wifi modules: Lupus kernel have them integrated into kernel, but with doomlord kernel you must flash wifi modules separately as ZIP files, from recovery.
To lazy to search it elsewhere, you can download it at the end of this post
Hi Bakisha,
Thank you so much! I was able to unbrick my r800i and it works with no problem now. Cheers!
Related
Guys i have royally screwed my girlfriends xperia arc s.
i have been trying to get it all working for about 6 hours but have made a complete mess.
Been trying to install doomkernal but it seems like i cant get any kernels to install at all..
Now the wifi is giving "error" and i have no idea how to fix this.
If i could please get some help urgently would be much appreciated.
If i can get the wifi fixed and some advice on how to get the kernels to install correctly would be much appreciated.
I have done the commands via fastboot to load the boot.img files but ever time i check the kernel in the phone it does not update?
Please help
Android version: 2.3.4
Baseband version: 8x55A-AAABQOAZM-203028D-56
Kernel Version: [email protected] #1
Build Number
4.0.2.A.0.42
ProficienTICS said:
Now the wifi is giving "error" and i have no idea how to fix this.
Click to expand...
Click to collapse
Have you flashed DooMLoRD's modules via recovery?
ProficienTICS said:
If i can get the wifi fixed and some advice on how to get the kernels to install correctly would be much appreciated.
Click to expand...
Click to collapse
DooMLoRD said:
[ how to install my kernel (v14 onwards) ]
download the boot.img & modules update.zip
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
save the modules update.zip to sdcard (on phone)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot flash boot boot.img
reboot phone and enter recovery
flash the wifi modules update.zip for my kernel
reboot phone and enjoy the kernel
Click to expand...
Click to collapse
For wifi , you need to flash a fix file provided by doomlord.... read the doomkernel's post completely..
yep i did, i flashed the kernel and it says it worked but in the phone info it does not say that doom kernel is installed.
Ive tried to install a few different kernels and none seem to be working?
downloading 'boot.img'...
(bootloader) USB download speed was 9203kB/s
OKAY [ 0.594s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.597s
Then it shows DoomLord image or free xperia image but once the phone boots up it doesnt seem to change the actual kernel..
ProficienTICS said:
yep i did, i flashed the kernel and it says it worked but in the phone info it does not say that doom kernel is installed.
Click to expand...
Click to collapse
And the modules?
Have you wiped data/cache/dalvik cache before flashing the ROM?
Nope can you elaborate sorry guys.
I have got my galaxy nexus running perfect first time but the sony seems much more difficult.
I have fixed the wifi now! Thanks.
http://forum.xda-developers.com/showthread.php?t=1424389
This is the rom i want to install.
I unlocked the bootloader via SE but have compeltely reset the phone.
What do i do in what order to get this working?
Sorry for this i have literally spent so many hours going over and over..
ProficienTICS said:
http://forum.xda-developers.com/showthread.php?t=1424389
This is the rom i want to install.
Click to expand...
Click to collapse
If you want this ROM, you've to install a different kernel.
Either DooMKernel for MIUI or BlendMIUI Kernel
ProficienTICS said:
What do i do in what order to get this working?
Click to expand...
Click to collapse
Place the ROM on the sdcard.
Install one of the kernels above using ADB.
Boot in the recovery and do a full wipe (also wipe dalvik cache ).
Install *.zip file from sdcard & reboot.
In order what i have been trying to do:
Root the phone with Easy rooting toolkit by DoomLord.
Install CWM with a CWM-Install file i downloaded
Install Kernel (Doesnt seem to work at all)
then install the ROM.
What am i missing or doing wrong? :\
Ok the phone is rooted, CMW is installed.
To install the kernel i go through CMD and do it via fastboot?
This method has not worked for any kernel ive tried to install - it pulls the picture of the kernel on the screen then reboots but doesnt update the kernel?
ProficienTICS said:
Ok the phone is rooted, CMW is installed.
To install the kernel i go through CMD and do it via fastboot?
This method has not worked for any kernel ive tried to install - it pulls the picture of the kernel on the screen then reboots but doesnt update the kernel?
Click to expand...
Click to collapse
Yes, use the command fastboot flash boot boot.img (don't forget to open CMD in the fastboot folder).
Then go into recovery, do a full wipe, install *.zip file from sdcard.
Ok MIUI DoomLord complete:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot boot boot.img
downloading 'boot.img'...
(bootloader) USB download speed was 9201kB/s
OKAY [ 0.719s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.003s]
finished. total time: 0.723s
It now is displaying the DoomKernel image on the arc but it is doing nothing - the image is sitting there and not moving
15 minutes now and the image still on the Xperia, nothing changing.
This is the problem i seem to keep running into - it wont let me add any kernels at all it just doesnt seem to work?
Anyone know why at allll?
Have you entered CWM after installing kernel?
It was still stuck on the DoomKernel image, only way to get out of it was battery pull.
What do i do :\
* Pulled the battery and im now in CWM. The phone boots up back aswell
Kernel Version exactly the same as before
Push kernel and then enter CWM!
Wipe everything and install ROM.
ok so this is normal?
What settings do i do exactly inside CWM?
Wipe Date/factory reset
Wipe cache partition
Wipe Dalvik Cache
Wipe Batter Stats
In any particular order?
Is there anyway to know the kernel installed correctly even tho it doesnt display in the about phone settings menu?
ProficienTICS said:
ok so this is normal?
What settings do i do exactly inside CWM?
Wipe Date/factory reset
Wipe cache partition
Wipe Dalvik Cache
Wipe Batter Stats
In any particular order?
Click to expand...
Click to collapse
No, you've written everything in the correct order.
Then install the ROM.
I have to put the rom back on the SD card - meaning i have to put debugging mode etc on - will i need to go back into CWM and wipe everything or just boot it up do the settings transfer the file and then go into recovery and install it?
Will it still be rooted etc and bootloader unlocked?
Put the ROM on your sdcard.
Shutdown device.
Boot in fastboot mode.
Push kernel using ADB.
Reboot and enter recovery.
Wipe everything.
Install *.zip from sdcard.
Reboot & enjoy.
The kernels are prerooted and you're not locking your BL, so of course it is still unlocked.
Done - installing miui now....
Praying this frigggen works !!!
Completed.
Reset.
Phone is stuck on Sony Ericsson screen and not doing anything.. FML.
5 minutes and still on Sony Ericsson.
man this is a joke :\
So another try..
Connect your device with your current ROM to a PC.
Put the ROM (*.zip file) on your sdcard.
Shutdown device.
Connect your device with fastboot mode (pressing menu button) to a PC.
Go to your fastboot folder.
Press shift key, right click and select "Open command window here".
Install kernel by using the command "fastboot flash boot boot.img".
After installing disconnect your device from PC.
Enter CWM recovery by pressing volume down button several times while booting.
Do a full wipe/factory reset, wipe cache, wipe dalvik cache.
Select install zip from sdcard.
Navigate to the folder you've saved the ROM and select it.
After installing select reboot system now.
I seem to have soft-bricked my one-v and could really use some pointers.
The things I did to get the phone bricked:
- Unlock the bootloader
- Try to flash miui.
Since this attempt the phone only boots until the "quietly brilliant" screen appears (with a red "This build is for development purposes only..." warning, but I guess this just indicates the bootloader is unlocked right?)
Since then I have installed ClockWorkMod recovery image. This seems to work, I can get in recovery mode and do things like install specific zip files from sdcard.
Unfortunately whatever ROM I try to flash the result is the same: boot until the quietly brilliant screen and then nothing.
For instance, I tried to flash shpongle_primou_20130521.zip (the One-V is the GSM version) using the following steps:
- Download the above zip file
- Extract boot.img
- Copy the above zip file to sdcard using another phone (cannot boot with the one-v so I cannot use it to write to sdcard)
- Put the sdcard back into the One-V
- Start the phone in fastboot mode and connect to USB
- use fastboot to flash boot.img (flashboot flash boot boot.img)
- Switch to recovery mode
- Use ClockWorkMod to flash the zip file
- Reboot the phone
Result: hang in quietly brilliant screen. If I just let the phone alone it seems to reboot every 5 minutes or so.
I fear that I am doing something stupid due to a lack of understanding of some basic concept. Can you guys give me some pointers on how to proceed to unbrick the phone?
it seems u have not flashed the correct kernel for shpongle (the boot img inside zip doesnt work)
try this kernel (ONLY FOR SHPONGLE) http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img
Also do factory reset from recovery everytime u flash a rom( u can backup data via titanium backup)
Also, your command command should be fastboot flash boot boot.img.
Sent from my HTC One V using xda app-developers app
Awesome, I got SHPONGLE to work. Installing the correct boot.img and clearing all data did the trick.
Now I can try to install miui again but I have a stable situation (and backup ) to work with.
Thanks a lot!
I have the same issue with my HTC one V but it is the virgin mobile version ( I live in the east coast of U.S.A.)
Will I be able to use the same solution?
which is the right ROM and Kernel for me?
i messed up with internal memory pretty badly.. i was using dual boot system till yesterday (system + cache + userdata + system2).. i wanted to flash stock pa gapps over cm12 but it was too big in size.. so i thought to increase system partition..so i took some space from cache n userdata partition...all partitions were created successfully..but then i was unable to flash even cm12.. so here's what i did... i reverted back all 4 partitions to original table (system + cache + userdata)... all partitions are just like the way they are supposed to be now...but now this is the scenario... m able to flash all roms but not able to boot any except official stable (50.0)... except official 50.0 rom, all roms are giving me a bootloop... so i tried to flash 50.0 rom couple of times but lost baseband... if i flash fastboot through miflash or adb, m able to flash all partitions individually except system partition.. check ss. i can access recovery... flash recovery, flash rom through recovery, access fastboot...but not able to boot (except official 50.0 rom) once flashed... not able to access network (baseband broken may be), to reboot, to power off after flashing 50.0...
is there still anything i can do to repair it..or should go to service center??
Edit: i observed that at each hard-reboot (soft reboot is not possible atm), i can see a folder being created called "ramdump" containing 1.25 gigs of multiple ramdump_modem_blah_blah_blah.elf files..
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone