it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
First off are you rooted? Do you have a custom recovery installed? Are you running a custom ROM or kernel? If you you have a custom recovery did you make a backup? If you can provide some more details I can try to help you out.
Sent from my SCH-I535 using xda premium
Alcatel OT5020t - Mediatek BOOTLOOP SOLVED!!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Pop c7 7041x
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
I have 7041x stuck in boot loop. Flashing a rom by CVM doesnt even help. Could you please tell us how you fixed yours.?
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
nabil_rachak said:
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
Click to expand...
Click to collapse
It's been so long since i messed with these Alcatel phones. But if i recall, you can take the rom zip or update zip, and you have to rename it to some special name. Then you put it on sd card and it'll install to phone.
But in your case, if you flashed wrong. There might be something else.
But either way. Since you can boot into recovery or bootloader you should be able to push stock firmware to device. You need to make sure you get the correct files for your device.
This is most i can tell you. I've been using samsung devices for past years and forgot alot about flashing devices such as this through adb.
All i can say is, at least it doesn't seem like your hard bricked. As long as you can get into bootloader mode or recovery, you should have a way to fix. Search and Google around! Good luck!
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Whenever learning to mess with phones and roms with adb and fast boot. As a lot of devices are different, but some simple key facts to follow are as follows.
Find out your devices partition layout (which partition is boot, system, recovery)
Don't mess with any other partition but them.
Always, always make a backup of all partitions with 'dd' command. And keep safe.
Need build prop
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
Where would I find the build prop bro? Thx
Related
its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
same thing here...CM9 causing CWM bootloops...WTF.
klutch said:
its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
Click to expand...
Click to collapse
i think you're going to need to use adb to push the rom files into your SD card
i believe the naked drivers are for adb
this is the command you're gonna need to use to push the files into your prime
Code:
adb push [insert rom here minus the bracket] /mnt/sdcard/
hope this helps~
i mean i know about the adb push but the problem is since that cause me some issues the CM9 nightlys it wont mount no mater wat i do wont mount
I deleted the external_sd folder with ES_fileexplorer, after that no app could recognize my usb_storrage.
Then I wanted to flash my galaxy note with Cyanogen again, but now CWM cant find the usb_storrage too.
I am also stuck @ CWM now :/
---------- Post added at 11:53 PM ---------- Previous post was at 11:21 PM ----------
smrtnik said:
I deleted the external_sd folder with ES_fileexplorer, after that no app could recognize my usb_storrage.
Then I wanted to flash my galaxy note with Cyanogen again, but now CWM cant find the usb_storrage too.
I am also stuck @ CWM now :/
Click to expand...
Click to collapse
Hmm seems like I formated my sd_card via CWM and CWM coldunt find any files ofc...now it works again. But unluckly it still can not find external_sd
klutch said:
i mean i know about the adb push but the problem is since that cause me some issues the CM9 nightlys it wont mount no mater wat i do wont mount
Click to expand...
Click to collapse
If you are trying to mount in cwm
I believe it's a known issue that doesn't work
so wat u trying to say that CM9 nitelys did the unknown issue?
klutch said:
its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
Click to expand...
Click to collapse
bro I was running the same CM9 and it screwed my Prime up like yours...CWM bootloop only...
my Prime was also not showing up when attached to the usb/computer...
after reading a bunch of very vague instructions and going through 5 or 6 different methods of trying to get it back I finally gave the following method a shot and it worked the first time (from the dev DiamondBack's thread)---
Code:
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
[CODE]Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
[/CODE]
this guy saved my panicked ass....thought my Prime was done...but these instructions brought it back...
well @ least u got urs running but i am still stuck wondering why i cant mount and the drivers are downloaded right i still dont get it i tried so many things and i went to W-XP and no luck @ all no i am scared that its bricked or something n spend 500 on a tablet n now wont work
I'm having the exact same issue, tried out CM9 and it now bootloops my prime into cwm. windows can't see the prime either when I connect it, so adb doesn't work, so when I type "adb shell" it comes back with "error: device not found"
before this, I was having issues with my tfp being recognized by windows. this is on 2 diff desktops (win7 and xp) and my laptop which is win7.
well my friend welcome to the same boat i have that same exact issue
ugh... does this mean I have a paperweight now?
jackmei2 said:
ugh... does this mean I have a paperweight now?
Click to expand...
Click to collapse
i dont know bro lol but all i know i dont want to drain a 500 buck tablet on the train because its going to hurt
have you tried contacting Asus regarding this issue? I think I might try and RMA the unit and complain that it won't connect to the PC or charge directly from the wall plug.
i mean if not mistaking theres no point contacting Asus when is hacked and bootloader unlocked its out of warrenty
yeah..it warns you like two or three times that unlocking the bootloader voids the warranty...
i know one of you has...but has everyone tried the method posted on the first page that saved the other guy?
when you're bootlooping, if you hold down the volume and power button for 5-10 seconds to get to recovery, does it automatically bootloop or does the text appear and give you the option to press volume up?
i was bootlooping and holding vol down and power for a long period of time, then manually going into recovery worked...
or does everything bootloop?..meaning can't even get into the rom itself
i'm asking because you mention cwm bootloop... if you try to force recovery by the above mentioned method (holding vol down and power during the bootloops until you get the option to go into recovery...) then just not hit anything and let it try to boot normally...
i know i'm not giving breakthrough advice, but hopefully some of this will help..
I thought I've seen a few posts where people have sent their TFP in for service even after they've unlocked it... it can't hurt to call and see what they say.
when I turn on my TFP it automatically finds CWM and boots right into it without me being able to press up to confirm. I think CM9 did this when I tried to boot directly from CM9 into recovery. so actually, I'm not bootlooping, I can get into CWM, but I can't do much else from there, not even turn off my TFP... I always have to wait for it to run out of power before it shuts off.
nono not that way bro i mean it ok ... u turn it on it comes the asus screen after that it go to CWM and if i reboot it does the same thing so basicly its no moving from asus just back to CWM and like i said its not mounting dont know why i tried XP and W7 n nothing intalled driver n nothing
I called Asus, and you can send in your unlocked TFP for repair... but they won't say how much it would cost, even if it is a hardware issue, they will still charge you. freaking lame...
so basicly i am stuck with my TF201 n cant do nothing damn
Hello. I'm super new to all android hacking stuff in general. I just recently bought a Letv one max. Super phone i love it. But its so damn limited when it comes to all that hacking stuff. I recently tried putting it into fastboot but all i get is a penguin on the screen. The linux penguin to be correct. I have been looking everywhere online and no one else has ever had this issue which i find so damn strange. I have installed adb and whatnot and got the correct drivers. I also opened up the command thing and typed in the codes etc, but it wont go past the damn penguin!!!!! Also when i flash twrp its all in Chinese and i cant do anything because i have no idea what it says.
I hope that someone on this forum can help me out because im so stuck. all i have is recovery mode nothing else its so frustrating. Anyone any suggestions would be highly recommended. Thanks.
Same problem
I have exactly the same problem with the Letv Pro (X800).
Did you find a fix for this?
I have got the same problem now, it won't go out of it either. What do i have to do?
spotkip said:
I have got the same problem now, it won't go out of it either. What do i have to do?
Click to expand...
Click to collapse
Seeing the penguin is normal. I have managed to fix the issues I have and I am running a custom ROM by Cuoco92, all thanks to the help I got from @simidisc.
I will assume that you have installed all appropriate USB drivers.
1. Visit http://bit.ly/1Q6irPH and download SEZIONE FIRMWARE and SEZIONE RECOVERY. Don't worry about this being in Italian - I don't speak Italian and managed no problem.
2. Copy the zip file from Sezione Firmware to your phone.
3. Unzip the the recovery file on your computer and connect your phone to your computer.
4. After unzipping TWRP, run "Install Over Fastboot".
5. Your phone will reboot and you will see the penguin. Just press VOLUME UP + POWER at the same time and your phone will reboot to TWRP.
6. You should now be able to flash the ROM, making sure to wipe cache, dalvik etc.
After i hold vol up and power, phone reboots in some kind of chinese recovery... what to do there? Not a clue what is written on the buttons, one has "update.zip" between the chinese text.
EDIT: problem solved, drivers from old phones was causing the problem.
Hello.
How it happened
I rooted my HTC One S, then flashed CyanogenMod on it. Used it for a few months, very happy with it. Then I tried to update - automatically, not manually (that was mistake number 1). The phone was then stuck in a bootloop into recovery. (Off>Recovery>Off>Recovery). I didnt know what to do, so I pressed 'Reset phone', or something like that. Since then, the problem has gotten much worse. Now there's a different bootloop: Off>HTC opening screen. That's it. Im desperately trying to access recovery mode, to flash a new ROM to fix the situation.
What did I try
1. Power + VolumeDown does nothing.
2. Installed the HTC One S toolkit. When pressing 'boot into recovery', it says 'device not found'.
3. Tried to boot into recovery from ABD tools, but it says device not found. I tried putting screenshots here, but XDA forum new user limitation doesnt let me. Anyway, if you add this to the imgur url, youll see the screenshots (sorry about this inconvenienace):
/SblBm3M
/6HEvZDk
TL;DR
Phone is stuck in a bootloop. Cant access recovery. Is there any way to fix this situation?
Thank you very much in advance for your time to help me out.
My phone model is Micromax Knight 2 E471.
It was working fine but it all happened all of a sudden. I was trying to connect my phone to the computer to access some file. Suddenly, I got a message on my screen that Encryption interrupted with some text and a button to reset. I rebooted the phone but it had the same message and I had no option but to click on the Reset button. From that time until now... it does not want to boot.
Then I searched for it on google and tried to start with two key combinations Power+VolumeUp and Power+VolumeDown. Power+VolumeDown. does not do anything but Power+VolumeUp get me to a recovery screen that says failed to mount /system, /sdcard, /cache and so many things (screenshot attached).
From the recovery option, I tried
1. wipe data/factory reset - doesnt do anything
2. wipe cache partition - doesnt do anything
Then I took it to Micromax service center. They said, OS needs to be reloaded. I paid 250/- and got it reloaded but still the issue was not resolved. Now there is a new problem. When I start the phone, it appears that it is rebooting but there is absolutely nothing on the screen. The screen is completely blank and black. The strange part is that, it keep vibrating after every minute or so which makes me feel that it is caught in a boot loop but nothing is displayed on the screen. The Service center guys says that there could either be a display issue or motherboard issue and in both cases, the hardware cost would be more. But I feel it is a software issue.
I again googled it and got to a page https://firmwarefile.com/micromax-e471 where I downloaded the firmware. The firmware folder had a file "8939_fastboot_all_images" which is a windows batch file. I installed the driver, executed the 8939_fastboot_all_images batchfile and went to the recovery screen I got from Power+VolumeUp key combination. Selected reboot to bootloader. I got lot of things in the ms-dos window but still the problem is unresolved.
I appreciate if someone here could help me what to do next.
Thanks
Something wrong with the mount points, maybe? Have you tried flashing a custom recovery like TWRP?
Adithya FRK said:
Something wrong with the mount points, maybe? Have you tried flashing a custom recovery like TWRP?
Click to expand...
Click to collapse
I cannot do anything with a screen with no display.
Can you tell me how to flash a custom recovery when the phone is in boot loop
Thanks
Your phone seems to have a Snapdragon SOC. Sorry but I'm pretty much useless with that. If it was an mtk you could have removed the battery and use SP Flash tool. Maybe someone else can help you with this.
Good luck.
bump
ACFH said:
First, dont post something like "bump", you can get ban.
2nd, if you cant flash, this tool may have. https://forum.xda-developers.com/showpost.php?p=71705583&postcount=5
This is only one tool can flash rom in this situation. If it not work, it could be hardware issue, not software.
Edit: after install qualcomn usb driver, make sure your phone is turn off, hold volume down button while plug usb cable (some phone need volume up, some need both of them, some doesnt need any button). Remember dont touch power button. If pc detect your phone like Qualcomm HS-USB QDLoader, you can using emmc.
Click to expand...
Click to collapse
Sorry for that!
First of all ToolStudio eMMC Download Tool link does not work. I downloaded the 50MB+ zip file and extracted, it asks for a password which I already put but it doesnt do anything.
Then I downloaded a downgraded version from here https://drive.google.com/drive/folders/0B7SVwjaFGLv_by1OSlMtaU9tQVE but it does not work. mMMC Download or Multil Download does not show RAM, Boot Image etc. The comments on that page also shows that there are so many people who are unable to do it. Do you know of a reliable download source for ToolStudio eMMC Download Tool?
Or do you have any other solution?
Thanks
AM also facing that problem with e471
Always showing flashing successfully .
But booting into recovery mode..
Need solution dear
Hello All
I find myself in a desperate situation.
I have rebooted to ffbm mode by mistake and my phone will not start.
I have just the white start screen with the wilefox logo...it does not get passed this.
I could do with some urgent help if there is anyone out there?...
Thanks
Update....I'm out of it...thank god...if anyone else finds themselves here then volume down and power button for a few seconds. Then you find yourself in the recovery mode where you can select reboot using the volume keys to navigate up/down. Rebooting then worked. What a relief!
mitchw1971 said:
Hello All
I find myself in a desperate situation.
I have rebooted to ffbm mode by mistake and my phone will not start.
I have just the white start screen with the wilefox logo...it does not get passed this.
I could do with some urgent help if there is anyone out there?...
Thanks
Update....I'm out of it...thank god...if anyone else finds themselves here then volume down and power button for a few seconds. Then you find yourself in the recovery mode where you can select reboot using the volume keys to navigate up/down. Rebooting then worked. What a relief!
Click to expand...
Click to collapse
Not working for me , help please ???, I had just unlocked my tab bootloader and flashed twrp recovery but instead of booting inyo recovery I booted into ffbm mode by pressing power mode , you are the only one who can help me please ??
I don't like to leave you high-and-dry...but I moved on from this phone already 3 years ago and its a distant memory.
All I can suggest is trying combinations of the buttons like. vol+ & vol- at the same time then press power and hold all 3 buttons.
Also on previous phones where I messed about and nearly killed the thing I found that holding the power button for AGES would eventually wake it up. It may be a waste of time but on occasions I found that just doing the same thing over and again eventually brought a result (although this is said to be the first sign of madness...so careful with that). Good luck with your endeavour...been there many times :S
mitchw1971 said:
I don't like to leave you high-and-dry...but I moved on from this phone already 3 years ago and its a distant memory.
All I can suggest is trying combinations of the buttons like. vol+ & vol- at the same time then press power and hold all 3 buttons.
Also on previous phones where I messed about and nearly killed the thing I found that holding the power button for AGES would eventually wake it up. It may be a waste of time but on occasions I found that just doing the same thing over and again eventually brought a result (although this is said to be the first sign of madness...so careful with that). Good luck with your endeavour...been there many times :S
Click to expand...
Click to collapse
May be I was wrong before that it is because of ffbm but here is the thing with which I had just suffered ... Yesterday just thought to go and unlock the device and root it with magisk, but when I booted into twrp , I found the twrp wasn't showing the device internal storage , so I searched on youtube and found that formatting data will help so I just did that rebooted again in twrp and it did work but while wiping other stuffs such as dalvik, cache , I accidentally wiped the system so I end up getting a lenovo tab 4 10 which can't boot anymore, And one more stuff is that my device is dm verity which is a biggest headache for me , I had almost 5 samsung phones and all rooted easily but the procedure of lenovo and their support is worst, I had decided to never go with any lenovo product in future but also can't waste my money on that tab : (
Btw ... Coming back to the topic while navigating to the device forum I found the o.p. has posted a system sparse image which can be used to restore the system but even after restoring it my device is not booting up only lenovo logo is popping up and then into fastboot mode, sadly there is no custom roms available for this device as I had also thought to flash the firmware using the guide but I am totally confused and scared about to not to do anything which will hard brick this device, I am still able to boot into recovery which I think is a strange think because after flashing sparse image it should be replaced by the stock recovery file, but as described no booting into system, I tried contacting in the xda forum but no one is replying , I even tried sending pm to the o.p. but no response .
I am conpletely newbie in this fastboot devices and the lack of support just sucks ,thanks for reading this and replying me if you have any suggestion from your previous experience then free fell to tell.
Akash23q2 said:
May be I was wrong before that it is because of ffbm but here is the thing with which I had just suffered ... Yesterday just thought to go and unlock the device and root it with magisk, but when I booted into twrp , I found the twrp wasn't showing the device internal storage , so I searched on youtube and found that formatting data will help so I just did that rebooted again in twrp and it did work but while wiping other stuffs such as dalvik, cache , I accidentally wiped the system so I end up getting a lenovo tab 4 10 which can't boot anymore, And one more stuff is that my device is dm verity which is a biggest headache for me , I had almost 5 samsung phones and all rooted easily but the procedure of lenovo and their support is worst, I had decided to never go with any lenovo product in future but also can't waste my money on that tab : (
Btw ... Coming back to the topic while navigating to the device forum I found the o.p. has posted a system sparse image which can be used to restore the system but even after restoring it my device is not booting up only lenovo logo is popping up and then into fastboot mode, sadly there is no custom roms available for this device as I had also thought to flash the firmware using the guide but I am totally confused and scared about to not to do anything which will hard brick this device, I am still able to boot into recovery which I think is a strange think because after flashing sparse image it should be replaced by the stock recovery file, but as described no booting into system, I tried contacting in the xda forum but no one is replying , I even tried sending pm to the o.p. but no response .
I am conpletely newbie in this fastboot devices and the lack of support just sucks ,thanks for reading this and replying me if you have any suggestion from your previous experience then free fell to tell.
Click to expand...
Click to collapse
Maybe you have this fixed by now.. I searched around a bit about this and found this:
https://blogthetech.com/flash-file-lenovo-tab-4-10-tb-x304l-firmware-download-stock-rom/
Only one step I'm unsure about and that is "You will need to power off your device and connect it to the PC while off."
On my Wileyfox device (different device, I know) I need to power off and then press and hold all buttons (power, vol +, vol -) until device vibrates and gives a blank screen/no screen, this is how to boot into EDL mode on my device.
Your device maybe works differently, try both ways.
This is probably the best way of unbricking your tablet and here is the firmware file you need:
TB-X304L (WiFi and LTE)
TB-X304F (WiFi only)
Do I understand you correctly that you also have a dm-verity check issue?
For that you need to be booted up and have USB debugging on, tablet connected to pc and you type in this command:
Code:
adb reboot "dm-verity enforcing"
It will reboot and dm-verity check should by then be fixed.
RavZ75 said:
Maybe you have this fixed by now.. I searched around a bit about this and found this:
https://blogthetech.com/flash-file-lenovo-tab-4-10-tb-x304l-firmware-download-stock-rom/
Only one step I'm unsure about and that is "You will need to power off your device and connect it to the PC while off."
On my Wileyfox device (different device, I know) I need to power off and then press and hold all buttons (power, vol +, vol -) until device vibrates and gives a blank screen/no screen, this is how to boot into EDL mode on my device.
Your device maybe works differently, try both ways.
This is probably the best way of unbricking your tablet and here is the firmware file you need:
TB-X304L (WiFi and LTE)
TB-X304F (WiFi only)
Do I understand you correctly that you also have a dm-verity check issue?
For that you need to be booted up and have USB debugging on, tablet connected to pc and you type in this command:
It will reboot and dm-verity check should by then be fixed.
Click to expand...
Click to collapse
Thanks for your effort, I had fixed my tab a week before by flashing the stock firmware but can you tell me what is the use of that dm verity commond.
And yes my tab is dm verity.
Akash23q2 said:
Thanks for your effort, I had fixed my tab a week before by flashing the stock firmware but can you tell me what is the use of that dm verity commond.
And yes my tab is dm verity.
Click to expand...
Click to collapse
I should've given it another read, you have headache over dm-verity cause you want to root your device with custom recovery and stuff like that. This command line will not do you anything, not anything you want anyways.
On a Wileyfox Swift 2 device there was an bad uptade that made dm-verity check fail, this command was used to "reset" dm-verity. I assumed you had a similar issue but now I'm sure yours is a different kind of issue.
You would probably want to find a way of disabling dm-verity on your device.
Made one search for it and found this:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
If it is only root you want you could get it with Magisk without flashing a custom recovery, you need the boot image of your device and you patch it with Magisk.
Then you flash the patched boot.img to your device. I believe this way works around dm-verity so is why I mention it.
https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
Akash23q2 said:
May be I was wrong before that it is because of ffbm but here is the thing with which I had just suffered ... Yesterday just thought to go and unlock the device and root it with magisk, but when I booted into twrp , I found the twrp wasn't showing the device internal storage , so I searched on youtube and found that formatting data will help so I just did that rebooted again in twrp and it did work but while wiping other stuffs such as dalvik, cache , I accidentally wiped the system so I end up getting a lenovo tab 4 10 which can't boot anymore, And one more stuff is that my device is dm verity which is a biggest headache for me , I had almost 5 samsung phones and all rooted easily but the procedure of lenovo and their support is worst, I had decided to never go with any lenovo product in future but also can't waste my money on that tab : (
Btw ... Coming back to the topic while navigating to the device forum I found the o.p. has posted a system sparse image which can be used to restore the system but even after restoring it my device is not booting up only lenovo logo is popping up and then into fastboot mode, sadly there is no custom roms available for this device as I had also thought to flash the firmware using the guide but I am totally confused and scared about to not to do anything which will hard brick this device, I am still able to boot into recovery which I think is a strange think because after flashing sparse image it should be replaced by the stock recovery file, but as described no booting into system, I tried contacting in the xda forum but no one is replying , I even tried sending pm to the o.p. but no response .
I am conpletely newbie in this fastboot devices and the lack of support just sucks ,thanks for reading this and replying me if you have any suggestion from your previous experience then free fell to tell.
Click to expand...
Click to collapse
Search on how to flash system with adb interface.