So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help
I have a VPAD7. It's stuck at the viewsonic Birds flashscreen. This is not a looping boot such has has been described in other threads -- it doesn't alternate between the flash screen and brief bursts of blank screen. It just sits there at the splash screen; I've left it for hours, and it just sits.
This all started when I rebooted to FTM (holding down the power button and vol down at the same time) in order to get this information:
* SWVer=3.240
* MODEL:FM6-0001
* HWVer:107
When I rebooted (power cycled) after that, it was stuck.
I have rooted the machine in the past (months and months ago), and installed CW mod. I *can* reboot the machine into recovery mode, holding both volume buttons when pressing the little pin reset button and then quickly pressing and holding the power button. I get the "ClockworkMod Recovery v2.5.1.2" screen. From there, I've tried wiping the cache, wiping the Davlik cache (although I get an error message when doing that about how it can't mount /dev/block/mmcblk0p2), flashing the update.zip on my SD Card (which is lakehousetech's Froyo 2.2 enhanced), and "wipe data/factory reset". I've also tried restoring from some of the backups I made in the past.
No matter what I do, if I try to do a straight boot, the device just hangs there at the splash screen. I can boot to FTM mode, and I can boot to recovery mode, but nothing seems to allow me to get the thing to actually boot all the way up and run.
Does anybody have any ideas of what might be wrong and how I might do something about it?
Thanks,
-Rob
You have new version of viewpad7. Maybe lakehouse rom is not compatible, please try other.
Sent from my ViewPad7 using xda premium
To OP, Froyo ROM that you've saved should be ITE (multi-touch screen) compatible with H/W ver. 107 - I don't think the custom ROM itself is the source of the problem, unless your saved CWM files are corrupted somehow ?
Do you have another mSD card, try formatting it first and copy the CWM folder/files on it, insert into Vpad7 and boot into Recovery, then do a full dalvik, cache and system/data wipe 3 times - before doing a Restore of the Froyo ROM.
Make sure your device is fully charged and let the ROM boot up & settled down, which can take as much as 10 minutes. If you have a 3G mobile Sim card, pull it out although it should NOT affect anything - just precautionary to rule out other factors.
If still NOT good, you will have to try flashing another custom ROM from scratch, I've been very happy with EU V1.7b ITE verision since last Sept/October - the original developer Amalgation hasn't been around, I think, and his link might still be broken for the download - hopefully, you have it saved before. Otherwise, post or PM me and I can provide a secured link for the untouched, original zip file as uploaded before - so that you can try to get the device back in working order.
Or, download the factory *.nb0 file and install it with the Viewsonic utility - for stock, unrooted condition as shipped. Then, you can use SuperOneClick to root, install CWM v2.x again (I personally like it better than the newer 4.x or 5.x verisons to set up A2SD) and resume playing with the limited choice of Roms out there now ...
Good luck & post your efforts/results back here to see whether other ideas might be useful. You didn't try to install/override with any overclocking kernel as none of them work with the ITE hardware, right :fingers-crossed:
Here's a link to some of my earlier notes written about the Vpad7 - in case you missed them. Many of the links are down & sadly, no longer available.
http://forum.xda-developers.com/showthread.php?t=1264647
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
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.