Related
Hello Everybody,
i am using this rom 4.3 from a while ago and i wanted to change it to the 4.4 rom
i decided to flash Omni 4.4.2 new rom from this url
http://forum.xda-developers.com/showthread.php?t=2487526
As per the installation instructions i went to download TWRP ver. 2.6.3.1 from here
http://techerrata.com/browse/twrp2/t03g
and i installed it through Odin, and when i tried flashing the rom through TWRP it says successful when i do factory reset and when i try to format data it says failed and when i try to flash the rom it says failed
it keep saying
e:/ unable to find partition size for "/data"
am not developer or expert, but i used to flash many roms for all my past android devices and this is my first time to see such error
well, the device still working when i exit TWRP and do system reboot my rom boot up normally and the device is perfectly working on my phonix 4.3 rom
but i noticed that Odin can not detect my device on the downloading mode anymore but it still can detect it if the device is turned on
So, could you guys advise about what exactly i had missed or damaged here? can i flash other roms? or recovery?
please give me some help here in deep details as am really new to such errors
Thanks a lot in advance and Happy New year for everybody
hey guys, any updates?
I m having the same problem, ay solution?
Mee too: http://forum.xda-developers.com/showpost.php?p=69313945&postcount=45
Mohamedloza said:
hey guys, any updates?
Click to expand...
Click to collapse
Jotapoggi said:
I m having the same problem, ay solution?
Click to expand...
Click to collapse
You still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Rifat Rezwan said:
I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Click to expand...
Click to collapse
apply update via zip. or adb sideload. you will get out of the issue
sukhwant717 said:
apply update via zip. or adb sideload. you will get out of the issue
Click to expand...
Click to collapse
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Rifat Rezwan said:
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Click to expand...
Click to collapse
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
timbernot said:
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
Click to expand...
Click to collapse
I've flashed AICP Nougat and gapps. still no luck. even with adb I cant boot anything other than twrp.
Read the link I posted in my first reply. Jeeese
timbernot said:
Read the link I posted in my first reply. Jeeese
Click to expand...
Click to collapse
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Rifat Rezwan said:
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Click to expand...
Click to collapse
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
timbernot said:
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
Click to expand...
Click to collapse
Cleanstock solved the problem. Thanks
Rifat Rezwan said:
Cleanstock solved the problem. Thanks
Click to expand...
Click to collapse
Nice
Back Cleanstock up so can revert back to it , flash away until bugs have been ironed out.
Above , switching between airplane mode and data works for me after a reboot and works flawlessly after .
Try AICP ROM
Its marvelous , regular updates
Hi, I have the same problem, actually it happened after updating to latest version of lineage os. I tried everything (various wipes and flashes, restoring stock backups, flashing cleanstock as suggested) but no luck.
I can't even reboot to fastboot through adb, my phone is just a recovery!
I can't imagine how this could impact, but I've just changed my lcd. But I started the update after changing the lcd, and the phone was working before with the previous LOS version, so...
EDIT: ok, I managed to make it work, I flashed TWRP 3.0.3-M3 (I was on 3.0.3-M2, I didn't try to reflash the same version). Too bad I needed just this, I wiped everything, even internal storage lol.
FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
dg89 said:
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
Click to expand...
Click to collapse
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
tiklmypikl said:
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
Click to expand...
Click to collapse
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
dg89 said:
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
Click to expand...
Click to collapse
What verison of TWRP are you on?
tiklmypikl said:
What verison of TWRP are you on?
Click to expand...
Click to collapse
right now it is on v2.8.7.0 and i tried to install the new version but it's not working
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.