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..
Related
As simple as that
Another question: if I perform "format system" and then reboot, will I be left without recovery?
I bought my device already rooted, but I understand that there is some sort of stock recovery. Is it true, if yes, what does it do?
In case I reboot after formating system and there will not be recovery as I suspect, I will be able to flash recovery image via fastboot as usual, right?
thanks
Format system will format the system partition, not the recovery.
Recovery will remain intact.
Thank you, but I would really like to understand how it works:
I know that the Internal memory devides into 3 partitions: system ,cach, data.
Which are the ROM. (This "ROM" is actually just flash memory isn't it? and is rewritable)
Where is the partition of the recovery if so?
Are there more partitions than those 3 in there?
Now when I come to think about it, I still don't know where the radio partition is, and where the data of bootloader is located.
I would still like to know what happens if you perform "format boot". Is it the partition where recovery is sitting or it refers to the memory partitioning (aka Hboot).
and That too
I bought my device already rooted, but I understand that there is some sort of stock recovery. What does a stock recovery allow to do?
Click to expand...
Click to collapse
thanks
There are actually more than those 3 partitions =)
There is:-
HBOOT - This is the bootloader its-self and contains the partition table
Boot - Contains the Kernel and a ramdisk used during startup
Recovery - Contains the recovery image
System - Contains the ROM installed on the device
Data - The internal memory, apps etc stored here
Cache - Pretty self explanatory =D It hold the cache =P
Radio - (Not too sure if this is on the NAND or not) Tells the radio chip how to communicate with your carrier etc (as far as I'm aware, someone feel free to correct me)
If you format boot, the phone will just go right to the bootloader without actually loading Android, but with a custom recovery it can be fixed easily by reflashing the ROM, nandroid restore, or by using fastboot to flash an existing boot.img. (Just a note here, flashing a Kernel wont fix this as the scripts used try to extract some parts from the existing boot.img, which isn't there after a format =P)
Assuming that you have an S-OFF HBOOT (Alpharev) you can flash any of those partitions with an image, using Fastboot as you mentioned, however, if you don't have S-OFF, you would have to do it through the Recovery (and you can’t flash HBOOT through recovery).
The phone does come with a stock Recovery Image, but this is very limited, Can only flash update.zip signed by HTC (again, might be wrong here), factory reset (Wipe data), reboot the phone and possibly some others.
Using either ClockworkMod Recovery or Amon_RA's recovery will let you flash custom ROMs, perform nandroid backups + restore (Boot, system + data) and a few other fancy things like wiping individual partitions =)
Hope this helps!
Thanks alot! you've explained it very clearly.
I would like just correct a very tiny mistake, probably unintentional - Factory reset is "wipe data", not "format system + data".
I got the answers that I wanted and more.
thanks again
It was unintentional =P I corrected incase someone happens upon the post.
Glad I could Help
wrong thread
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!
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
... title - a guide would be nice aswell :/
sure! https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
Just be sure that you reenter fastboot after rebooting - by pressing vol-. Then it won´t erase your data.
To be fully sure boot twrp, install it, flash aboot from 9.6.11.0 - else you will get "your system got destroyed" while booting twrp and then you can save your data partition to external sd card - now even if it would try to erase your data, you will have a backup.
And after reboot you will see, if it still tries to erase data - then it will go again and again to twrp... To solve that, reflash stock kernel - just in case.
I flashed AOSP_10_Quack_Phh-Treble_v208 many times last night.
but always failed,bootloop.
My step:
unlocked + TWRP
1.factory reset + format /data(or not)
2.flash V208.img to system image
3.format /data or not,reboot
My phone showed Redmi-logo and dm-verity error,
and bootloop.
anybody successed?
Could Somebody teach me how to flash GSI?
Maybe to flash AOSP 9?
It's reassuring to see you have attempted multiple times to flash another ROM and haven't hard bricked your phone.
My guess is you need to flash the dm-verity remove zip file. I'm assuming you have selected AVB 2.0 in TWRP? That's all I can think of but I haven't tried anything as clearly I don't have balls as big as yours
I used these following steps from tvardero :
Flash stock
Flash twrp
Make a backup of system and data (to get back into stock if needed)
Format data -> yes
Flash GSI you want to
To flash another GSI or revert to stock you use your backup of system partition.
NEVER EVER RESTORE ANYTHING ELSE THAN SYSTEM OR DATA, softbrick imminent
I try many GSI-ROM
Most bootloop,even I format /data,disable dm-verity/AVB 2.0 (TWRP by wzsx150)
My steps is
fomat /data,reboot to twrp
wipe /system ,2cache and flash gsi.img(Maybe resize /system to flash gapps)
flash magisk
disable dm-verity/AVB 2.0 with TWRP by wzsx150,or flash disabler.ZIP
GSI ROMs had some different bugs,brightness control,NO mobile signal,
sound,nfc-sim support,googlepay ,bank app etc.,
Really nice to see some testings. I hope we have some some development for our devices