So i finally made the jump to ics 4.0....i chose flexreaper and installed it got into the os and it gave me a error " Unfortunately, Maps has stopped." and now i cannot get wifi to work at all wont even let me turn it on can somebody help. i even wen as far as to go from ics flexreaper r11 -> r12 and still the same issue. I dont know what i am doing wrong.
bfoster said:
So i finally made the jump to ics 4.0....i chose flexreaper and installed it got into the os and it gave me a error " Unfortunately, Maps has stopped." and now i cannot get wifi to work at all wont even let me turn it on can somebody help. i even wen as far as to go from ics flexreaper r11 -> r12 and still the same issue. I dont know what i am doing wrong.
Click to expand...
Click to collapse
Have you done a full wipe before flashing Flexreaper?
bfoster said:
So i finally made the jump to ics 4.0....i chose flexreaper and installed it got into the os and it gave me a error " Unfortunately, Maps has stopped." and now i cannot get wifi to work at all wont even let me turn it on can somebody help. i even wen as far as to go from ics flexreaper r11 -> r12 and still the same issue. I dont know what i am doing wrong.
Click to expand...
Click to collapse
Do a data factory reset and reboot. If this does not fix it try a fresh download and reinstall the rom.
Yep. Sounds like a "wipe/format" issue. Somebody hasn't done their "Data" wipes and formats. (because they don't want to re-install their apps)
Generally you can get away with this when coming from a previous recent release of a rom, but coming from a different rom, you should always follow the wipe/format steps.
In RA Recovery;
Wipe Data/Factory Reset (includes format)
Wipe cach's (includes format)
Wipe android.secure (optional)
System generally gets formatted on rom install.
.
Ok i thought i did that but maybe i did not, But i will try it but the only problem now is it wont let me get into recovery it acts like it wants to try to get into recovery but then gives me the droid with exclamation. I already did a hard reset and it is a fresh install of the software. I want to completely reset it but when i try it just says i am going back to android v 3.2.1 and i am still unable to get into the recovery by pressing vol down+power. Also i tried to use the acer recovery app and it says that my device is not supported. Even tho it is a acer a500. I am lost i would like to get the table back to the original state then try to get it rooted. any ideals?
bfoster said:
Ok i thought i did that but maybe i did not, But i will try it but the only problem now is it wont let me get into recovery it acts like it wants to try to get into recovery but then gives me the droid with exclamation. I already did a hard reset and it is a fresh install of the software. I want to completely reset it but when i try it just says i am going back to android v 3.2.1 and i am still unable to get into the recovery by pressing vol down+power. Also i tried to use the acer recovery app and it says that my device is not supported. Even tho it is a acer a500. I am lost i would like to get the table back to the original state then try to get it rooted. any ideals?
Click to expand...
Click to collapse
Well, in this case, it sounds like your Flexreaper install destroyed your recovery image. Probably messed with the bootloader, as it is becoming more frequent these days. Basically there are at least 2 versions of it, one for ICS bootloader, and the other for HC bootloader.
If you can get your Wifi working, you can probably run the AcerRecovery from the market, and try installing a recovery image. If not, here is the author's thread where you can download it and install through a file manager.
http://forum.xda-developers.com/showthread.php?t=1588189
Should be able to get a CWM recovery back. If you get devblk errors, try installing RA Recovery.
Also, make sure you are still rooted.
And from what I remember, the recovery app will tell you that it's incorrect version, but I've read where it says to ignore it. Seems this happens when coming off the ICS Beta's.
ok
I got the tablet to go back to its original software(not rooted) out of box. But when i try to load into the recovery still tells me the same thing and will not allow me to get into the recovery. And when i try to use acer recovery it still says that error message even with the link you provided me. I was able to gain Wifi back and i can update just unable to flash a Rom or root. I don't know what to do i think what you said makes sense about the boot loader being fubared. But i dont know what to do to change that.
There is nothing in the Flexreaper rom that changes the bootloader.
It will boot or it won't,
Same with recovery , there is not one thing that will replace or change your recovery.
You posted that you didn't even know that you did a full wipe or not, so maybe you flashed something that you didn't know?
I flash rom everyday for testing and never had big problems with my test roms.
The problems you described in your first post are all caused by not following installation instructions.
If I was you restore your tablet to stock and start all over again.
Related
I tried to use SuperOneClick to root my phone and it seemed to work. The program came back saying I successfully rooted my phone.
I then went to ClockworkMod to install cyanogen and clicked on the appropriate boxes to begin the download process for cyanogen 6.0 stable mod and ran it.
My phone rebooted and started to run some scripts.
Now, the phone just reboots to the green mytouch screen and continues to loop like that and I have no idea what to do.
I can get into fastboot on the mt3g and when I do, my pc makes the sound that states that the phone is connected but when I try to get into the mytouch, using adb, my pc cant access it but when I plug up my G2, I can see the serial number and such showing that it is connected.
I tried to follow the fastboot driver installation page but it didn't seem to work.
Bottom line is I would really enjoy a functional MT3G in either the regular form or cyanogen (which is why im in this predicament now )
For the the record,
I was running 1.6 but got the OTA update for 2.2 before I ended up blowing up my phone.
Thanks for reading this and any aid would be greatly appreciated.
UPDATED:
I found something called SAPPIMG.NBH that allowed me load Android 1.5 onto my phone. I now am back to a functioning device but still, I am super stuck on trying to get cyanogen onto my device. Any helpful hints? From what you read above, did I miss something?
Thanks again.
... Sadness... I have been bashing my face against this mt3g and haven't been able to get cyanogenmod on this phone for the life of me. I have tried all of the builds from 5.08 up to RC1 of 6.10 and I just get the infinite loop at the cyanogen boot up screen. I even tried to flash 2.23.XXXX radio to see if it gets past the boot loop and it does not. Anybody have any insights into my issue?
Thanks,
You must go into recovery mode(boot up by holding down home + power). That will get you to Clockworkmod recovery(I am assuming since you said you downloaded using Clockwork app). From there you need to wipe cache, and anything else you can wipe. Then try installing Cyanogenmod after that. Without wiping the there is not enough space to install and it causes a bootloop.
I'm in the same boat, I'm stuck in a boot loop and I cannot get any ROM to fully load in. I'm using clockwork recovery Radio 2.22 32B.
I tried wiping everything but that still doesnt seem to work. I noticed when I try wiping Davlik cache I dont see any message on the bottom. I thought it would normally give me some sort of message stating that it is wiping davlik or something so maybe it isnt actually wiping it?
Is there some other way to make sure davlik is wiped? Or something else I can do. I just want the phone to boot up at this point. I can get into recovery but thats it.
I know I shouldve done a backup but dumb me was such in a rush I completely forgot, I know im a idiot...
Het I found that same .img file and also reverted back to 1.5 then just went up to 2.2 not sure what was wrong but Rom I put on just went into a boot loop. Maybe it was clockwork recovery.
Sent from my ADR6300 using XDA App
the padawan becomes the master... Sort of...
The problem is that you cannot go directly to 2.2 from 1.5. You have to do the incremental upgrades that take you from 1.5 to 1.6 then 1.6 to 2.2
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
After ICSroot.exe by blackthund3r, it said successful and done, but i wasn't rooted.
posted HERE
So, I'd tried Root Many Androids
now everything it boot up try to go in, i get message saying "Unfortunately, System UI has stopped" and kick me out.
This force me to install ROM, because when I went in the recovery screen it was looking for UPDATE.zip file.
1. How can I fix this issue
2. If not, how can I restore to factory from bootup
3. or what rom out there is good for a500 4.0.3, if i must
urgggg
nevermind, i was able to hard reset power + up + toggle.
Redid ics root 2.0 and font is installed.
Want to try JB, but wait and see how stable it is.
NautTboy said:
After ICSroot.exe by blackthund3r, it said successful and done, but i wasn't rooted.
posted HERE
So, I'd tried Root Many Androids
now everything it boot up try to go in, i get message saying "Unfortunately, System UI has stopped" and kick me out.
This force me to install ROM, because when I went in the recovery screen it was looking for UPDATE.zip file.
1. How can I fix this issue
2. If not, how can I restore to factory from bootup
3. or what rom out there is good for a500 4.0.3, if i must
urgggg
Click to expand...
Click to collapse
I was rooting my device and was successful l in that. I flashed TWRP and Magisk and after that I decided to install a custom ROM. While going for it I again wiped the - Delvik Cache, System, Data and Cache. And when I tried installing that ROM it doesn't gets install. Moreover I can't boot into System anymore and now I'm stucked at the screen saying "Your device has been unlocked and can't be trusted." Also the screen is showing "ID:N/A"
So please please please help me with this problem ASAP. I can't use my phone now please and I regret for what I've done.
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
NZedPred said:
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
Click to expand...
Click to collapse
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?
engtika said:
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?
Click to expand...
Click to collapse
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone
NZedPred said:
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone
Click to expand...
Click to collapse
Thanks for the information you provided regarding my problem. Now I've installed the Stock ROM and my dead phone is back to life. ?