Good Day! I am new here and I recently bought a Malata zPad, I have been reading all the post here and I am convinced that the G Tablet and the zPad are the same. When I bought my zPad its already loaded with apps and I can say that it is already rooted I can see Vegan-Tab text when its loading assuming it is the ROM already flashed on the device. It is already flash with Clockworkmod Recovery, after reading all the tutorials about flashing, I downloaded a ROM (zPad Clean 3.0) for the G Tablet and flash it using CWM the process was good and it was successfully installed, but the problem is I was stuck on Loading screen, I was able to recover my backup with CMW, I tried different ROM for the G Tablet still with no success.
I tried downgrading to lower version CMW v08 , I flash with nvflash the flashing was successful but when I try to boot in recovery it just stuck on loading screen.
I can still boot normally and can use my zPad my only problem now is I can't seem to flash it with different roms . I hope someone can help me with this problem, you guys here are great more power, Thanks and God bless.
got interesst is this, too. I have an Olipad 100 and it sucks, looks like an Malata zPad T2
Related
I've been running Vegan 5.1 for quite some time and would like to try out the new experimental edition. I've gone through the process defined in multiple places in the development thread... install, wipe, etc...
Every ginger ROM I've tried (Vegan and Corwin) gets stuck after reboot. With Vegan, it stops at the 'Devs' boot screen and with Corwin at the 'Android' screen. In each case, I've left the device at those screens for over 45 minutes and nothing happens. Multiple installs with both ROM's and no luck.
I went back and installed Vegan 5.1 after all of the above and it installed successfully with no issues.
I'm running clockwork 0.8.
What am I missing?
Thanks
This is becoming a common problem with the new gtabs. You need to nvflash your tab to stock. You have 2 partitions that are reversed and nvflash will fix it. The instructions are in the dev section
thebadfrog said:
This is becoming a common problem with the new gtabs. You need to nvflash your tab to stock. You have 2 partitions that are reversed and nvflash will fix it. The instructions are in the dev section
Click to expand...
Click to collapse
thanks... i will give it a shot.
Hey friends,
I tried to upgrade and flash my tf to the newest ARHD or Revolver ics roms yesterday, coming from Prime 2.1. Therefore I wanted to use my rogue cwm recovery and made sure to wipe the tablet before i started to flash.
At first I thought, the light edition of the full wipe script from ARHD would do, but neither of both roms mentioned came beyond the first screen (nvidia tegra etc.) after installation.
Then I tried the wipe function of cwm, but that simply did what the script did I believe (leaving the internal storage untouched), which didn't succeed, too.
Finally I wiped my tablet with the "real" full wipe script and tried installing again, and again without any success.
So I used a nvflashable version of the stock ics i found in this forum (I have a B50), which eventually resulted in a working ics installation. I gave each of the other roms up to 10 minutes for the first screen before I stpped the try, and stock ics skipped this screen after 2 seconds after its successful installation.
I remembered, that I already had this behaviour when I was trying to flash a custom rom first, right after I rooted it, but with a different recovery back then (must have been roach's).
So I wanted to ask you if you have any ideas why this happens. I mean, I don't believe that it's all because of bad flashs. Both roms were stored in different locations, one on the sd, one on the internal memory. It's very inconvenient that I always have to wipe all partitions including the internal storage when I want to change my rom and there are only the roms available to me which have a nvflash version.
Thank you in advance, I hope I didn't write too much.
Hi all i own a Spice MI 410 phone, i tried to install CM9 custom ROM on it using clock work recovery mod but each time after successful updation my phone doesn't reboot! its stuck at boot screen. If i restore it it runs fine. I really want to install a custom rom please help. I cleared all data, dalvik, cache etc. I even tried it using rom manager where it automatically cleans cache but each time its stuck in boot loop! i am really at lost at what to do whole Saturday of mine was wasted doing this, please guide thanks.
i'm in the same condition like you, still trying to get it right :crying:
kuroroku said:
i'm in the same condition like you, still trying to get it right :crying:
Click to expand...
Click to collapse
Sorry to know, well if you find any solution then do share it here.
1) Are you sure the ROM you downloaded is for your phone?
2) Did you try downloading the ROM again? (You could have gotten a bad download.)
Sounds like a soft brick i had this happen several times. Start up in recovery, restore backed up rom, reboot, redownload the rom you are trying to flash, boot recovery, wipe your cache delv, and factory, than try again. If that doesnt work the rom you downloaded is bad. If you didnt make a recovery, take your SD out put it in your computer, download a rom go it that you know definitely works, put it back in your phone and than juat flash the working rom.
Fixing Permission while in recovery has done miraculous things for me and I did not see that you mentioned that. Also on some devices (HTC namely) if you are not running the right bootloader version some ROM's won't boot, EX running CyanogenMod ROM on hboot 1.58. Search your device forum and see if the answer lies there...and whatever it is that is causing this, once resolved please pot back so that others can learn from your experience.
Well the problem is my phone (Spice CSL MI 410) comes in different models in different countries and even different types like cdma/GSM etc. Its Spice CSL MI 410,Wellcom, Motorola Truimph, Huwaie Ideos X6 etc etc So i don't know if this Rom fits my model as here only Ideos x6 forum is present and i downloaded from there, still i will try to redownload it
First of all, thanks for all the hard work you guys do.
I have a problem with my tf101 running a Cyanomod. I tried searching on the forum, but there are so many keywords i don't even know how to input a proper query, so sorry if the problem has already been covered.
My tf101 was working just fine, i mounted a new rom (a nightly based on Jelly Bean 4.1.2), everything was nice and smooth, until one day i forgot to plug the charger to my tablet. The battery ran down to 0%, the first time it ever happened. Since then, everytime i try to power my tablet it gets stuck on the cyanogenmod rotating logo. I have to force reboot it several times before it starts working again, even if the battery id completely charged.
The first time it happened i tried wiping all data as well as the cache, i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly. Until the battery accident, everything was perfect.
Why is this happening? Is there a way to fix it?
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
ZigaG said:
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
Click to expand...
Click to collapse
Yeah it does, but only after countless attempts. If i do nothing and let it go, it gets stuck on the cyanogen logo forever.
I will try your solution and let you know, thanks.
Which recovery are you using ?
TWRP is the one to use, CWM has issues
I have been running CWM recovery and installing Wingray nightlies on my MZ604 without any problem for more than a year. A couple of days ago I flashed what I think was a partially downloaded ROM. This soft bricked my Xoom (somewhat unsurprisingly). I ended up in a boot loop so I used this method http://www.xoomforums.com/forum/motorola-xoom-development/18743-how-flash-sbf-rsd-method.html to get out of it.
That worked fine leaving me with a stock Xoom running 3.1.
I then unlocked the bootloader and flashed CWM Touch using adb. I then booted into recovery and flashed the universal Xoom root from here http://forum.xda-developers.com/showthread.php?t=1242241.
Again, this worked fine so now I had what appeared to be a fully functional Xoom running CWM Touch and 3.1. So far, so good.
The final step was to install a recent ROM so I booted into recovery again, flashed the latest Wingray nighly and the GApps package as I have done on numerous occasions (after doing a factory reset and wiping the cache and the Dalvik cache). This appeared to work just as it has always done but now my Xoom just sits at the M logo and nothing else happens. I can still boot into CWM Touch but my Xoom won't get past the M logo in normal boot.
Since everything seemed to work exactly as I would expect right up to the final boot, I'm somewhat mystified as to what is wrong. Can anyone give me any suggestions as to what to do next?
Now I can actually help you. I saw this a day ago but did not respond yet because I did not test my method.
It's been stated by a few in the eos 4 wingray thread that nightlies 204-205 are TEST builds. Only one person said that but from what everyone else is experiencing this appears to be true. You are not alone mine was bootlooping and never getting past the splash animation either.
You don't need to fix or flash a new recovery. All you have to do is use a lower build such as 203 and you'll be fine. I'm testing some roms right now and they work fine now. I did upgrade to twrp recovery as well.
I'm sorry you went through the whole boot loader process again.
At least it's a simple fix. I'd recommend monitoring the eos4 thread and see when people post about newer builds working. I'm sure 206 will fix everything.
Best of luck.
Thanks for the suggestion but unfortunately it didn't work. I did get past the M logo and the multicoloured splash screen appeared but it just got stuck there.
I tried going back to 203 and that didn't work. I also tried going way back to 155 (with the appropriate Google apps package) and that didn't work either.
I am starting to wonder if there is something about the way I am flashing these that isn't working. I have done it so many times that I am rather baffled as to what is going on this time but I think I shall try flashing using Odin and see if that gets me any further. It's all rather frustrating as I haven't been able to use my Xoom for days now.
I have now fixed this although I am not absolutely sure whether my diagnosis is correct.
By flashing Wingray 203 and a very old GApps package, I got past the splash screen. The Google setup program then crashed but at least it had booted. I then tried 203 and the second most recent GApps package (dating from January I think) and it worked.
My guess is that there is some weird interaction between the most recent versions of Wingray and the most recent GApps package (and possibly other factors) but at least my Xoom now works.