i'm facing a problem after switching from cwm v6.0.1.2 to twrp v2.4.3.0. every time i do something in recovery, i get the message E : Invalid block device on '/boot emmc' , 'boot' , 24. i'm able to install flashable zips. i'm also able to create backups, but restore results in bootloop. somebody, please help.
m0han said:
i'm facing a problem after switching from cwm v6.0.1.2 to twrp v2.4.3.0. every time i do something in recovery, i get the message E : Invalid block device on '/boot emmc' , 'boot' , 24. i'm able to install flashable zips. i'm also able to create backups, but restore results in bootloop. somebody, please help.
Click to expand...
Click to collapse
Why don't you switch back to CWM?
ibshar said:
Why don't you switch back to CWM?
Click to expand...
Click to collapse
tired of using hardware keys. want touch. any solid recommendation?
m0han said:
tired of using hardware keys. want touch. any solid recommendation?
Click to expand...
Click to collapse
Use twrp 2.5.0.0 ur problem will be solved.
Sent from my A110 using xda app-developers app
m0han said:
tired of using hardware keys. want touch. any solid recommendation?
Click to expand...
Click to collapse
Nah, not a fan of Touch Recovery as it's a little risky!
ibshar said:
Why don't you switch back to CWM?
Click to expand...
Click to collapse
ibshar said:
Nah, not a fan of Touch Recovery as it's a little risky!
Click to expand...
Click to collapse
not sure if it's risky, but i get put off by errors messages, esp. if they can't be solved. although backup & restore worked fine, this one prevented me from installing a new/diff. rom. so, it's back to cwm v6.0.2.8 for now......
m0han said:
not sure if it's risky, but i get put off by errors messages, esp. if they can't be solved. although backup & restore worked fine, this one prevented me from installing a new/diff. rom. so, it's back to cwm v6.0.2.8 for now......
Click to expand...
Click to collapse
So you took my advice but No Thanks! .. (just kidding)
ibshar said:
So you took my advice but No Thanks! .. (just kidding)
Click to expand...
Click to collapse
i was coming from cwm and the 'return ticket' was already there my search for a 'solid' touch recovery continues....
Don't worry that error dosent gives any problem...
Everyone who he's installed twrp 2.4 on mmx a110 has that error displayed....
Related
hi,
i am using clockworkmod recovery 5.0.28 and i cant make nandroid backup everytime i try i am facing "Could not mount sd-ext. sd-ext backup may not be supported on this device. Skipping backup of sd-ext" this error.can i fix this or shuold i flash twrp recovery?
thanks..sorry for poor english
theanswer.3 said:
hi,
i am using clockworkmod recovery 5.0.28 and i cant make nandroid backup everytime i try i am facing "Could not mount sd-ext. sd-ext backup may not be supported on this device. Skipping backup of sd-ext" this error.can i fix this or shuold i flash twrp recovery?
thanks..sorry for poor english
Click to expand...
Click to collapse
Yes flash twrp....which will be soon uploaded by bhargz!
MF101 said:
Yes flash twrp....which will be soon uploaded by bhargz!
Click to expand...
Click to collapse
thanks for reply can you give me the download link?
Currently we have 2.2.2.1 but wait for a while 2.3.3.0 is going to be uploaded ! U can find them in android dev section
theanswer.3 said:
thanks for reply can you give me the download link?
Click to expand...
Click to collapse
Here is the link
http://forum.xda-developers.com/showthread.php?p=32159351
Hit thanks if helped
sent from my htc pico
hi everyone i have a problem with this rom i do a nandroid backup i buy the flash image gui i flash the boot file boot into recovery i do a full wipe but when i try to instal team venom rom its star and stop in 7.00% and then says reboot or save log i press reboot and the cellphone stay in white screen with red lettlers but now i can restore because the boot.img file its not the same of my backup i hope somebody help me
sorry for my english
MAMBO3000 said:
hi everyone i have a problem with this rom i do a nandroid backup i buy the flash image gui i flash the boot file boot into recovery i do a full wipe but when i try to instal team venom rom its star and stop in 7.00% and then says reboot or save log i press reboot and the cellphone stay in white screen with red lettlers but now i can restore because the boot.img file its not the same of my backup i hope somebody help me
sorry for my english
Click to expand...
Click to collapse
Which recovery are you on?
dwarriors1987 said:
Which recovery are you on?
Click to expand...
Click to collapse
TWRP
MAMBO3000 said:
TWRP
Click to expand...
Click to collapse
Sorry, I'm just now seeing this but if you haven't solved it yet, I would recommend trying out ClockWorkMod Recovery and then flashing...I had the same issue and switching recoveries fixed it.
dwarriors1987 said:
Sorry, I'm just now seeing this but if you haven't solved it yet, I would recommend trying out ClockWorkMod Recovery and then flashing...I had the same issue and switching recoveries fixed it.
Click to expand...
Click to collapse
thanx for your answer i already fix it but thanx for your help but now my problem is i want to change rom but i cant i want to flash illusion rom but when i try to flash dont even start just stop i think its because the kernel but i dont know how to update kernel
Yeah it probably is the kernel, you have to update the hboot...here's a guide for it. http://forum.xda-developers.com/showthread.php?t=2322755
i'm facing a problem after switching from cwm v6.0.1.2 to twrp v2.4.3.0. every time i do something in recovery, i get the message E : Invalid block device on '/boot emmc' , 'boot' , 24. i'm able to install flashable zips. i'm also able to create backups, but restore results in bootloop. somebody, please help.
m0han said:
i'm facing a problem after switching from cwm v6.0.1.2 to twrp v2.4.3.0. every time i do something in recovery, i get the message E : Invalid block device on '/boot emmc' , 'boot' , 24. i'm able to install flashable zips. i'm also able to create backups, but restore results in bootloop. somebody, please help.
Click to expand...
Click to collapse
Bro use twrp 2.5.0.0 which is somewhere in our forum it is working perfectly for me & backup/ restore working flawlessly without any problem.
Sent from my A110 using xda app-developers app
kuldeepraj said:
Bro use twrp 2.5.0.0 which is somewhere in our forum it is working perfectly for me & backup/ restore working flawlessly without any problem.
Click to expand...
Click to collapse
thanks. but, i read this post and also this by @varun.chitre15. any way to get rid of that "invalid block device" error?
m0han said:
thanks. but, i read this post and also this by @varun.chitre15. any way to get rid of that "invalid block device" error?
Click to expand...
Click to collapse
Its not developed by @varun chitre15 it is ported from other device and it is in our forum.
Ok got thread
http://forum.xda-developers.com/showthread.php?p=44737963
Hit thanks if helped
Sent from my A110 using xda app-developers app
Hi. Please help. I have been running CM10.1 on my rooted tablet and I decided to try CM11. I don't know what I have done but CM11 did not work so I tried to go back to CM10.1, and that just gets stuck on the boot screen. I have tried several different Roms and they all get stuck on the boot screen. The only Rom that will work is CM9.1? I don't know what I could have done to cause this. I am running Philz Touch 6.12.8. Any help would be greatly appreciated.
Thanks
mattmust said:
Hi. Please help. I have been running CM10.1 on my rooted tablet and I decided to try CM11. I don't know what I have done but CM11 did not work so I tried to go back to CM10.1, and that just gets stuck on the boot screen. I have tried several different Roms and they all get stuck on the boot screen. The only Rom that will work is CM9.1? I don't know what I could have done to cause this. I am running Philz Touch 6.12.8. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I think you need to replace your recovery twrp. Because I replace CM10 or CM11 works fine
http://forum.xda-developers.com/showthread.php?t=2548257
blue_drt29 said:
I think you need to replace your recovery twrp. Because I replace CM10 or CM11 works fine
http://forum.xda-developers.com/showthread.php?t=2548257
Click to expand...
Click to collapse
Yeah. I tried that and it is still the same. Thanks though
mattmust said:
Yeah. I tried that and it is still the same. Thanks though
Click to expand...
Click to collapse
i think you should flash back to stock then root then try new recovery and then flash the rom
i think the problem will be solved i do have same problem
Mohdsultan said:
i think you should flash back to stock then root then try new recovery and then flash the rom
i think the problem will be solved i do have same problem
Click to expand...
Click to collapse
I can't even flash back to stock. It still gets stuck on boot screen.
Thanks
Make sure you did a factory reset and format /system before.
Android-Andi said:
Make sure you did a factory reset and format /system before.
Click to expand...
Click to collapse
Yeah. I already did that. Thanks
@mattmust is it a verizon Tab?
Android-Andi said:
@mattmust is it a verizon Tab?
Click to expand...
Click to collapse
I'm not sure. I don't think so.
I also noticed when in recovery it says "E: unable to mount '/efs'"
mattmust said:
I'm not sure. I don't think so.
I also noticed when in recovery it says "E: unable to mount '/efs'"
Click to expand...
Click to collapse
Your EFS seems to be broken for some reason... that´s why it won´t boot into system....
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
Android-Andi said:
Your EFS seems to be broken for some reason... that´s why it won´t boot into system....
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
Click to expand...
Click to collapse
Yeah. That makes sense as I did put a version of CWM touch on. And the trouble started after that. Just need to try and find a solution to sort it now. Thanks for your help
mattmust said:
Yeah. That makes sense as I did put a version of CWM touch on. And the trouble started after that. Just need to try and find a solution to sort it now. Thanks for your help
Click to expand...
Click to collapse
Latest CWM Touch for our Device 6.0.2.7 ... i am sure you used a file for a different device and that broke your EFS!
Do you still have the file? you can upload it for me and send me a private message with the link, i can take a look on it. Please don't post the file here in the thread (i do not like to see someone else flashing it and breaking his efs).
Hey guys,
I was trying to back up my current ROM (Purity w/Code Blue Kernel) using nandroid. But, when I do a quick backup (Set recovery as TWRP), it says that I don't have enough disk space. I have more than 25gb free, lol. This has happened several times - I've factory reset and also flashed a factory image. Nothing works. I would appreciate a solution.
Thanks
Try Philz Touch and see if it throws the same error?
vin4yak said:
Try Philz Touch and see if it throws the same error?
Click to expand...
Click to collapse
Trying now, thanks.
Skippery said:
Not exactly sure what that is, sorry, noob here. I Googled it and I assume it's an improvement to CWM?
Click to expand...
Click to collapse
Its a recovery, originally based on CWM but far superior.
rootSU said:
Its a recovery, originally based on CWM but far superior.
Click to expand...
Click to collapse
I tried flashing the zip from actually your page I believe. Nothing showed up
Skippery said:
I tried flashing the zip from actually your page I believe. Nothing showed up
Click to expand...
Click to collapse
Sorry what?
rootSU said:
Sorry what?
Click to expand...
Click to collapse
I was just saying that I downloaded the zip from your page. And I just rebooted 3 times and it seems that it's working now. Thanks!
vin4yak said:
Try Philz Touch and see if it throws the same error?
Click to expand...
Click to collapse
Yeah, just tried and I get the same error.
Skippery said:
Yeah, just tried and I get the same error.
Click to expand...
Click to collapse
Please provide logs and screenshot from recovery
Also screenshot from storage menu.
Or just backup your entire sdcard to computer then try and backup
Sent from my Nexus 5 using Tapatalk