Related
My phone wont boot, so can i install a rom from clockworkrecovery?
agy1995 said:
My phone wont boot, so can i install a rom from clockworkrecovery?
Click to expand...
Click to collapse
Won't boot in what way? Can you get into fastboot and/or recovery? Since you're asking about CWM, I'm assuming you can get into it.
If you did a Nandroid backup (the main point of CWM for me), you could try just restoring it. If you didn't, I'd try a wipe all settings and then reboot. You should be able to get back to a virgin state on the main OS that way.
I can get into it, the problem is i erase all data on my phone. Thanks in advance!
???
Is there any way i can get my phone back up and running restoring everything from clockworkmod?
agy1995 said:
I can get into it, the problem is i erase all data on my phone. Thanks in advance!
Click to expand...
Click to collapse
agy1995 said:
Is there any way i can get my phone back up and running restoring everything from clockworkmod?
Click to expand...
Click to collapse
I'm still confused what your problem is.
You say the phone won't boot, but then you talk about erased data.
What exactly did you do to the phone? What was the last few things you did before you "broke" it?
What happens when you try to boot the phone (ie., it's powered off and you press the power button)? How far in the boot process does it go?
If your problem is that the phone boots but all your data is gone, there's no way to get back unless it auto-syncs down from Google, or you used a backup program like Titanium, or you made a nandroid backup in CWM.
If you made a nandroid, you should just be able to boot into CWM, select backup and restore and then restore your backup.
This is what happened....
I tried to replace my fonts in system that are supposed to work on a different phone. Then when i tried to boot up the phone was stuck on the silver google logo. Now, after that i went into clock work recovery and formated everything in the mounts and storage menu. After reinstalling the phones boot img, my phone freezes at the google logo. I can still get into the clockworkmod recovery. I never backed it up, but tried to use a nandroid someone posted online but i get a md5 mismatch.
Again, thank you for all your help!
agy1995 said:
I tried to replace my fonts in system that are supposed to work on a different phone. Then when i tried to boot up the phone was stuck on the silver google logo. Now, after that i went into clock work recovery and formated everything in the mounts and storage menu. After reinstalling the phones boot img, my phone freezes at the google logo. I can still get into the clockworkmod recovery. I never backed it up, but tried to use a nandroid someone posted online but i get a md5 mismatch.
Again, thank you for all your help!
Click to expand...
Click to collapse
The Modaco rom(http://forum.xda-developers.com/showthread.php?t=883985) should work just fine. Put it on the USB storage then in Clockwork go to "Install from zip."
i have a problem almost like that but my rom manager open but wont even backup current rom or anything, my titanium back doesn't backup either. it said i could not acquire root privileges, this app will not work, please vertify that you rom is rooted and includes busybox, i have busybox and it's rooted. i guess this happen when i update the google update last night from rom manager. what should i do
willyalmanzar said:
i have a problem almost like that but my rom manager open but wont even backup current rom or anything, my titanium back doesn't backup either. it said i could not acquire root privileges, this app will not work, please vertify that you rom is rooted and includes busybox, i have busybox and it's rooted. i guess this happen when i update the google update last night from rom manager. what should i do
Click to expand...
Click to collapse
Known issue. There is a thread in the Development section(http://forum.xda-developers.com/showthread.php?t=884499). The OTA "broke root."
Ouch. Now I understand.
In the future, always make a nandroid backup before messing around with things, easiest way to recover.
I see you're looking for help in this thread. Maybe they can help you.
You could also try flashing Doc's or Paul's roms also in that section.
rom
I tried that custom rom... still didnt work. Im going to give it another shot!
agy1995 said:
I tried that custom rom... still didnt work. Im going to give it another shot!
Click to expand...
Click to collapse
Did you wipe/factory reset before attempting to install? I realize that you're pretty much wiped at the moment, but always best to start with that.
unremarked said:
Did you wipe/factory reset before attempting to install? I realize that you're pretty much wiped at the moment, but always best to start with that.
Click to expand...
Click to collapse
I did that + i am using version 3.0 clockwork. Still frozen on the google screen.
agy1995 said:
I did that + i am using version 3.0 clockwork. Still frozen on the google screen.
Click to expand...
Click to collapse
You've tried another NAND backup, besides the one that MD5 mismatched, yar? Be careful not to rename it, as that can cause the mismatch.
Nope
Nope i didnt try any...
Do i have to rename it to update.zip?
Do i have to rename it to update.zip?
agy1995 said:
Do i have to rename it to update.zip?
Click to expand...
Click to collapse
The custom rom? No, you just go into recovery, wipe/factory reset, install from SD card, then navigate to where you put the .zip on the SD card.
I see you did try the 2.3.1 NAND backup in the development section. Try downloading it again on your PC, unzip it, then place the new folder on the clockworkmod's backup folder on your SD card. Again, do not rename it.
Im trying it now.
Im trying it now.
agy1995 said:
Im trying it now.
Click to expand...
Click to collapse
Be warned that if you do get the NAND to restore, you may lose clockwork recovery. I know I did when I first tried to use it.
Don't panic though, because you can fastboot flash clockwork back on from the bootloader.
I am pushing the files....
I am pushing the files....
I have a Nexus S i9023 with stock 2.3.6, unroot and everything, basically i didn't do a thing. Now, I want to update to 4.0.3, but since the ota doesn't show up i want to do it manually: i've searched the post but i can't find an how-to
http://forum.xda-developers.com/showthread.php?t=1063664
I downloaded the file for my 9023t, but i don't know what to do with it
Jerry69 said:
I downloaded the file for my 9023t, but i don't know what to do with it
Click to expand...
Click to collapse
oh come on, a few minutes of searching would have enlightened you.
if you downloaded the update: rename file to update.zip, put in root of your device, boot into recovery mode and install through it.
Danke, i tried to search "FLASH ZIP" but there were sooooo many topics unrelated (like flashing custom roms ecc)
Jerry69 said:
I downloaded the file for my 9023t, but i don't know what to do with it
Click to expand...
Click to collapse
Jerry69 said:
Danke, i tried to search "FLASH ZIP" but there were sooooo many topics unrelated (like flashing custom roms ecc)
Click to expand...
Click to collapse
http://lmgtfy.com/?q=nexus+s+flash+ics+4.0.3+update+zdnet
[/snark]
Thanks, that made me feel stupid enough Flashing right now
Thanks, everything done
Why after flashing clockwork (and made a nandroid backup) when i access recovery screen stays black?!?
Jerry69 said:
Why after flashing clockwork (and made a nandroid backup) when i access recovery screen stays black?!?
Click to expand...
Click to collapse
because OTA has a script that reinstalls stock recovery every boot.
The black screen is because the ics recovery for 9023 does not turn backlight on, a bright light should show it up.
To stop the recovery reinstall you need to rename /ect/recovery-from-boot.p and /system/install-recovery.sh
Sent from my ice cream powered Nexus S
rename in something like file.old.p or something specific?
DarkhShadow said:
...
To stop the recovery reinstall you need to rename /ect/recovery-from-boot.p and /system/install-recovery.sh
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
i have same problem, can you please explain this little more? or give some link where is explained how to do this? i need to rename this to what?
thank you very much
Thanks guys, everything ok now
jurvyx said:
i have same problem, can you please explain this little more? or give some link where is explained how to do this? i need to rename this to what?
thank you very much
Click to expand...
Click to collapse
You need root and a root file explorer, just rename those files then flash custom recovery and it will stick
Sent from my ice cream powered Nexus S
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
duloz said:
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow, that's so bull**** haha. Thanks for the quick reply
bulldozed said:
Wow, that's so bull**** haha. Thanks for the quick reply
Click to expand...
Click to collapse
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
bulldozed said:
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
Click to expand...
Click to collapse
That's not the clock work recovery. It's the bootloader. That's where you need to be to flash the image though.
First download the Nexus 7 image from https://developers.google.com/android/nexus/images#nakasijro03d
Once you have downloaded it extract the file twice until you see image-nakasi-jro03d.zip
Take that zip and move it to the directory where you have fastboot on your computer.
Open your command prompt pointing at that directory.
Then, type:
Code:
fastboot devices
if it returns a number you are good to go.
Next type:
Code:
fastboot -w update image-nakasi-jro03d.zip
This will wipe your user data and restore stock recovery. But you should be good to go.
geez, just reflash your rom, youll be ok.
El Daddy said:
snip
Click to expand...
Click to collapse
absolute legend. Thanks for the detailed reply, really appreciate it! I will give that a shot right now.
EDIT: haha took me five minutes to get it reflashed to stock. thanks again!
simms22 said:
geez, just reflash your rom, youll be ok.
Click to expand...
Click to collapse
haha sorry if my posts were a bit over the top, I was just sitting in bed having a play (with my Nexus 7........), then all of a sudden my tablet is seemingly wrecked simply from trying to change the battery icon... I FREAKED
Did something similar myself.
Just downloaded the factory image and flashed just the system.img file using fastboot and rerooted. A few system apps played up, most were fixed by wiping the cache but i had to delete all data from the contacts app, it resynced fine anyway.
To clarify extract the factory image to get the system.img and use the following
fastboot flash system system.img
Just rewrites the system partition.
Sent from my Nexus 7 using Tapatalk 2
The same thing happened to me trying to change the wifi icon. I guess Rom Toolbox doesn't play well with the Nexus 7?
Same thing on Galaxy Nexus... stumbled upon this thread searching for a solution. Was thinking we could restore from the backup that was made when swapping icons, but I guess that's not the case?
bulldozed said:
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
Click to expand...
Click to collapse
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Master Ramy said:
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Click to expand...
Click to collapse
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
mlj11 said:
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
Click to expand...
Click to collapse
Yes, the post was in response to the OP talking about losing the soft keys and such Due to the different nature of your issue, I've sent you an email instead of responding here, so that we don't clog up this thread
Hi All
Wondering if i could get any help from you guys
Ok so i flashed my a500 a year or so ago with a new boot loader the twrp 2.1.3 and loaded a then upto date rom, so today thought i'd update it to ROM] [A500] Android 4.3 [CM10.2 Unofficial] Build 5, Put it on to my sd card booted into recovery wiped cache and and system then flashed the rom.
So it booted into the rom but i kept getting an error msg saying somthing was stopping, the only way i could get out of it was to hold the power button to switch off. I switched it back on only to get to the boot screen and not go any further.
So this is where it gets wierd, i downloaded another rom and flashed that only to get the same problem, I've now tried 4 or 5 different roms with the same boot loop.
So i can get to recovery and flash a new rom etc but cannot get any further
Does anyone have any help they could offer as Im stuck
Many thanks
Same issue. Updated TWRP to 2.6.3, no avail. I bet if you look at the logs in TWRP you'll see you're not able to mount any partition. Also there is another thread on here that has the same issue. I believe it to be caused by the 4.3 CM Rom, haven't figured out a fix for it yet but if you format EVERYTHING, reinstall the rom you can boot once, but any reboot will put you right back where you are.
Filemanager shows the files are still present in /system /cache /data, so I'm not sure what this points to.
Does look good then :crying:
You'd think that by being still able to get into recovery there would be a chance just to flash a different rom and it would sort it
Not sure what to do next now, was just looking around and was going to reflash my recovery and try then but looks like you have tried that
Really wished I'd left alone now
You'd think, but I'm betting this has to do with the partition table getting corrupted or something of that nature.
unsivil_audio said:
You'd think, but I'm betting this has to do with the partition table getting corrupted or something of that nature.
Click to expand...
Click to collapse
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
I;ve tried wiping everything then tried flashing that particular rom but same out come, havent tried the babsector.rar dl yet so will give that a bash, question with that though will i have to reflash to the new bootloaders again so i can run the cm10 ?
Thanks
No m8 the babsector file will auto flash v8/cwm, just be sure to follow the instructions. Run bat file, boot DIRECTLY to cwm, wipe, flash rom and reboot. There is a 2nd bat file u should run next, but most folks have found they're all good after just running the first one...so up to u...if u get any errors pls post the output
Cheers dibb
Sent from my GT-I9300 using Tapatalk 4
dibb_nz said:
No m8 the babsector file will auto flash v8/cwm, just be sure to follow the instructions. Run bat file, boot DIRECTLY to cwm, wipe, flash rom and reboot. There is a 2nd bat file u should run next, but most folks have found they're all good after just running the first one...so up to u...if u get any errors pls post the output
Cheers dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Your an absolute genius pal, this worked a treat when all other things failed
Follow this procedure to the letter and you can't fail
Thanks again mate you've saved my tablet
Sent from my GT-I9300 using Tapatalk 2
avenger79 said:
Your an absolute genius pal, this worked a treat when all other things failed
Follow this procedure to the letter and you can't fail
Thanks again mate you've saved my tablet
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
awsum dude glad you got it
dibb
EDIT: @avenger79, pls edit the title of your thread to [SOLVED] to help others having a similar issue, thanks m8
Thanks guys. This worked for me as well.
dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
Any idea if this babsector might fix this issue here?
http://forum.xda-developers.com/showthread.php?t=2456947
NapalmDawn said:
Any idea if this babsector might fix this issue here?
http://forum.xda-developers.com/showthread.php?t=2456947
Click to expand...
Click to collapse
Well it certainly won't hurt...but first do full a format data, cache, system via fastboot so myt wanna do nandroid backup b4 hand.
Then "fastboot boot recovery" and flash yr rom of choice...
I do know some have had issues with latestv twrp, not sure if there's a fix yet or not. ..
Sent from my GT-I9300 using Tapatalk 4
dibb_nz said:
Well it certainly won't hurt...but first do full a format data, cache, system via fastboot so myt wanna do nandroid backup b4 hand.
Then "fastboot boot recovery" and flash yr rom of choice...
I do know some have had issues with latestv twrp, not sure if there's a fix yet or not. ..
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
I'm baaaacckkkk :good: Looks like a lot of bricks while I was gone.
Moscow Desire said:
I'm baaaacckkkk :good: Looks like a lot of bricks while I was gone.
Click to expand...
Click to collapse
Haha welcome home MD, trust your sufficiently rested and ready to help out, lol! !
First off, is there a stock 501 update.zip or EUu around or can the 501'ers jyst use evil alex instead...any issues at all with alex? And would it run ok on the a500?
Babsector.rar file is becoming the goto for unbricking. Not sure if you've looked at it or know how it works but there are 2 bat files to run. Of late folks have just run the first one then wiped and flashed a rom without running the 2nd. With no adverse affects. Would u know the reasoning behind running the 2nd bat. Hate to think I've been putting folks wrong...eeek...
Its gr8 to see the 500's still popular as ever, judging by the flurry of 'help I'm bricked' posts lately. Unfortunately as u know I am no dev, so I haven't been able to help out with rom issues...hence my question earlier re: evil alex!
Anyways MD awsum to have u back helping out an keeping an eye on us all
Cheers n thanx again
dibb
Sent from my GT-I9300 using Tapatalk 4
dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
Just FYI, this fixed both of my friends tablets (his and is his wifes ended up soft bricked after reboot). I'm suspecting this is TWRP's (2.1.3) fault but can't be sure. Even reinstalled the CM 10.2 rom and put it through several reboots, no problem now.
unsivil_audio said:
Just FYI, this fixed both of my friends tablets (his and is his wifes ended up soft bricked after reboot). I'm suspecting this is TWRP's (2.1.3) fault but can't be sure. Even reinstalled the CM 10.2 rom and put it through several reboots, no problem now.
Click to expand...
Click to collapse
Fantastic! Which 10.2 are u running?
Sent from my GT-I9300 using Tapatalk 4
This one, the same one that bricked both of them in the first place.
We put hers on the CM 4.1.2 Flex you recommended. Both running like a champ again.:good:
unsivil_audio said:
This one, the same one that bricked both of them in the first place.
We put hers on the CM 4.1.2 Flex you recommended. Both running like a champ again.:good:
Click to expand...
Click to collapse
Some folks have reported playstore probs with Flex so interesting you haven't. When u ran babsector, did u use both bat files? And what wipes did u do in cwm?? I'm just trying to nail down why some are having probs
Sent from my GT-I9300 using Tapatalk 4
I'll have to ask my buddy today if he's had any play store problems.
I did, but I just figured I probably better follow the instructions to the T. I don't really get whats different about the 2nd file 501 b.bat, seemed like it did the same thing.
dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
You SIR are a LIFE SAVER! :good:
I used your babsector.rar and was able to get my A500 working again!
Thank you very, very, very much!! :laugh:
Hello everyone I ma have problems on creating a nandroidbackup using TWRP 3.2.3.0
When I try to do a full backup, this error (createTarfork() process ended with error:255) pops up. Please help anyone
darko454 said:
Hello everyone I ma have problems on creating a nandroidbackup using TWRP 3.2.3.0
When I try to do a full backup, this error (createTarfork() process ended with error:255) pops up. Please help anyone
Click to expand...
Click to collapse
You need to look at /tmp/recovery.log while in recovery (adb pull it if you have to). Look in it for the last file that it tried to read before it gave the error. Your options are either delete that file or pull it then delete it. However, the file is corrupt in some way and the backup will never finish.
Sorry I a noob on this, I was able to get the recovery.log and Attached it but i dont have any idea where to find the error. Please help
thanks
darko454 said:
Sorry I a noob on this, I was able to get the recovery.log and Attached it but i dont have any idea where to find the error. Please help
thanks
Click to expand...
Click to collapse
I think It would be the " BASICDREAMS" but i cant seem how to delete it.. Would it be better to erase everything and start from the beginning? Im not sure what to do.
darko454 said:
I think It would be the " BASICDREAMS" but i cant seem how to delete it.. Would it be better to erase everything and start from the beginning? Im not sure what to do.
Click to expand...
Click to collapse
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
fuzzydorito said:
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
Click to expand...
Click to collapse
Thanks!!!
fuzzydorito said:
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
Click to expand...
Click to collapse
I just tried the "remove_basicdreams.zip "and says script succeeded but when i try to backup again it still has the same error.
what should i do next ?
thanks