Hi
So I rooted my Gioneed Gpad G1 and CWM and everything was smooth until I got the idea of flashing a custom ROM using this idiot's post here
//needrom.com/mobile/gionee-gn800-custom-rom-leetsleek-v1-0//
So while I understand there is a probability that the phone would work perfectly are 50-50, mine falls in the unfortunate category.
I flashed the rom and the installation was succesful. However, upon reboot, my phone is stuck at the boot screen showing "Gionee". I can access the custom recover, and have tried cleaning cache, and the devlick cache, and formatting the phone. Nothing works.
Since this was my first experience with rooting, I had no idea about the nandroid backup, until I saw the posts later on, albeit too late.
So, my question is, is there any remote possibilty that I can get my phone back in working condition? Any kind of response would be appreciated.
PS: I write under this forum since paranoid android is one the best custom roms there is, and unfortunately, neither this nor any other rom is available for Gionee.
Related
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.
Hi everybody,
when trying to install a custom ROM (PAC Nightly) on the TF201 to upgrade it from the stock 4.1.1, I first rooted and unlocked it and installed TWRP 2.6 and did a full backup.
Then I wiped Dalvik, System and Cache.
However, PAC did not get past its boot animation and when I tried to restore the backup from before, the tablet is stuck at the ASUS-Boot Logo (with "Device is unlocked" notification).
I am not sure what to do now. as the title says, TWRP still works and it does show up in fastboot.
Thanks in advance.
/e: I do have the impression that it was a lot easier on my Nexus S. :-/ The question is: is something broken and I have to try the unbrick solution or can i fix it by creatively wiping everything and just install some other ROM?
Well, another try and it worked. Strange. Phew.
Oh, brilliant. Now I have some questions about the ROM itself but may not post it inits thread. :|
If someone accientally reads this: I have no sounds (ring, notification etc), however they are displayed in the list.
Sound itself works, tested in the YT-app. Keybord clicks also.
Is this a matter of the PAC ROM or...well, where are they stored anyway? I suppose the files are floarting around the internet somewhere.
Hi, all! I'm sorry if this is in the wrong section, but I'm having a hard time trying to understand the different forums.
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
Thanks in advance, and I apologise if this is in the wrong forum!
You might want to ask to the rom thread for some help or ask in this section,
Galaxy Ace S5830 Q&A, Help & Troubleshooting
Anyway, I will try to help. If your custom recovery is support backup and restore (and advanced restore) your rom (check your custom recovery thread), try to backup your phone rom for now, so you could restore it back when solution not working.
Try to reflash the rom again without wipe data and reboot. If still in bootloop try to wipe data and reboot, see if that phone still bootloop.
If phone is successfully boot, go back to recovery and go to advanced restore, restore only data and then reboot. If still not working, then just full restore back to the phone to state before since I have no idea anymore.
That is the option I only know for now. However, try to ask help on section I link above or the rom thread before try this one, since I only familiar with Galaxy Gio (really similar to Ace) in the past.
I tried what you suggested but no positive results, really. I managed to boot after a full wipe, but restoring data locked it back into a bootloop. I'll try posting it in the other section.
Thanks.
Hi,
I´m hoping someone is reading this and is willing to help me out.
I recently bought the ME102A and succesfully rooted it with Kingo. Yesterday I used the info from androtab.info to install the CWM recovery, which worked great! I then accidently wiped the ASUS ROM from the tablet, trying to install a custom ROM. I should have read better, seeing as there are no custom ROM´s yet for the ME102A. I the tried almost every option I can think of, trying to get the original firmware back on the tablet but to no avail. I've read countless of threads and sites, but have yet to find the solution for me.
I´m currently back to stock recovery, unable to use the tablet. I can only boot into Android system recovery. I tried to install the custom CWM image found in this thread, as well as the stock image found on adrotab.info. I´ve seen almonst every error mentioned on this site and on others, like the "assert failed" and the "<waiting for device>" as well as "Installation aborted"...
I'm at a loss and am hoping some of you good folks can help me bring the life back to my tablet. It's not my first time flashing ROM's so I understand some of the basics (although reading apparently isn't my strongest point...) and can work a little with ADB and FastBoot etc. I have however no understanding of RKAndroidTool and the likes. But I am willing to try almost everything at this point...
Regards, Arie
If you are still around I ran into a very similar problem today and managed to bring the memo pad back to life. It may not be exactly the same problem you had but I would be more than happy to help if you are still around
This is basically what i managed to do
Issues on current version
official update cannot be installed. you need to modify updater-script as follows
remove
assert(getprop("ro.build.asus.sku") == "XX");
replace
write_raw_image(package_extract_file("YYYY"), "ZZZZ");
with
package_extract_file("YYYY", "/dev/block/platform/emmc/by-name/ZZZZ");
(it seems it needs more fixes for OTA update...)
touch(swipe) does not work.
arievandriel said:
Hi,
I´m hoping someone is reading this and is willing to help me out.
I recently bought the ME102A and succesfully rooted it with Kingo. Yesterday I used the info from androtab.info to install the CWM recovery, which worked great! I then accidently wiped the ASUS ROM from the tablet, trying to install a custom ROM. I should have read better, seeing as there are no custom ROM´s yet for the ME102A. I the tried almost every option I can think of, trying to get the original firmware back on the tablet but to no avail. I've read countless of threads and sites, but have yet to find the solution for me.
I´m currently back to stock recovery, unable to use the tablet. I can only boot into Android system recovery. I tried to install the custom CWM image found in this thread, as well as the stock image found on adrotab.info. I´ve seen almonst every error mentioned on this site and on others, like the "assert failed" and the "<waiting for device>" as well as "Installation aborted"...
I'm at a loss and am hoping some of you good folks can help me bring the life back to my tablet. It's not my first time flashing ROM's so I understand some of the basics (although reading apparently isn't my strongest point...) and can work a little with ADB and FastBoot etc. I have however no understanding of RKAndroidTool and the likes. But I am willing to try almost everything at this point...
Regards, Arie
Click to expand...
Click to collapse