Related
Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone
I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?
A little help please about the subject?
Thank you
ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....
Does you disabled the usb debugging before flashing?
Yes I do, but nothing change,
Thanks
if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.
I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks
I had used this. Try with it
P.S. sorry for my bad english.
Tried, the same errors,
Thanks
I don't know. Sorry. By the time i had used that.
I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium
I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..
@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm
i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!
I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!
-edit- nevermind, I didn't notice you were running revolution.
If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.
Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019
Awesome! That worked great. Thanks Horndroid!
hi
motoroladefy plus MB526 from australian
i copy many of files to SD (downloaded till i finsh my monthly limit) change the name to update.zin files
same msg
now my phone cant start system freezing @ motorola logo
when i chioce power and down button then down + up open a windows wrote this :
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
copy may ROMs to SD and i choiced 2.apply update from sd
show me after check this msg:
E: signature veification failed
install aborted
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote: Error validating image file ..when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
how can i solve this please
can i get australian service center for motoroladefy plus email ?
thank you
Questions go in the Q&A section
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
need help
MarcinRN said:
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
Click to expand...
Click to collapse
in first thank you
yes installed 2ndinit and super1c,rom manger = cwm and <3e rerovery>..(byaway still <3e> see it when i prss down volum:
Android system recovery <3e> isnt mean its not stack recovery?
in first the recovery boot work with all option ( backup,recovery,back,...) i think it mean root succeed _saw blue LED
but cant install ROM ...E:signature verification failed Installation aborted)-nothing accept to install same error ..thats mean NO i cant install any ROM
restarted and wiped data,cache, again and again + (system formt) after restart cant see all option @ recovery mode only that 4 option:
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
this time i have use both -,+ volum to enter recoverymode!
i dont remember i choice unroot under recoverymode!
about LED now only white when i off the phone and connect cable but not charging only white LED
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected​
dlshad said:
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected​
Click to expand...
Click to collapse
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
MarcinRN said:
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
Click to expand...
Click to collapse
thank you
im sure im in bootloader the white fonts black backgraound
usb conected andthe RSD see the phone
the secount of your note
i install may of files from here:
http://sbf.droid-developers.org/umts_jordanplus/list.php
all of that same error
sure i remove last 2 word (.gz)
in past i upgrate to 2.3.6 seccesed from official site
when i bought it they said its unlocked maybe not factory unlocked is that help!
in recovery mode there is <32> isnt mean its rooted not stock recovery
can i add backup option to recovery mode coz i have backup file
any help
thank you
dlshad said:
sure i remove last 2 word (.gz)
Click to expand...
Click to collapse
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Downloaded sbf file but unable to unpack
MarcinRN said:
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Click to expand...
Click to collapse
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
rahulpillai said:
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
Click to expand...
Click to collapse
what error does it actually give? which program are you unpacking archive with?
E:signature verification failed. Installation aborted; after rooting spice mi 500
Just yesterday I rooted my spice mi 500. Was fine untill i paid and downloaded a bunch of pro apps like ROM Manager Pro, and ran some scripts, thinking it might be routine clean up. but after running some script...I am only getting the followin message. I can see my spice phone in device manager on my PC, and drivers are up to date. I am unable to use the USB properly as the PC is not recognizing my device...Pls help asap. thanks.
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
Plese Help... !!!
:crying:
I m having MMX A25 .
i have installed CWM 5.x.x.x.version
whenever i tried to install custom Rom in it .
It just shows me an error SIGNATURE VERIFICATION FAILED
i am totally stuck,.. !! plese somebody help me out to install custom rom.
Help would b appriciated. :good:
I have same problem with galaxy s gt i9000 Froyo with recovery 3e.
I read that this recovery doesn't allow installation of files not signed.
Tried many but no luck I'm rooted but cannot install even a custom recovery.
Did you find the solution please.
Thanks
Sent from my GT-I9000 using Tapatalk 2
Greetings all,
So I have been trying to redo my Wanam KitKat install due to the foldermount issue and I ran into a couple of issues. Now before someone comments about that awesome app from the app store, yes I use it I just have other reasons to try and get a clean install going.
So first things first, I Odin flash the latest CWM by Sameer, do the necessary wipes and start the install. I then get this error message:
set_perm: some changes failed
E:Error in /data/media/0/ROM Install/wanamlite-v40-nb3.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
So I power down the device and Odin flash the latest CWM Touch version and I still get the above message. I then flash Philz Touch 6.07.9 and voila, it installs without an issue. Now one of my other issues to resolve this foldermount issue is because any recovery other than the Philz version mentioned (even the latest Philz) fails to flash any files and has an issue seeing my internal storage.
So I Odin back to my earliest ICS version and try from there. Now the CWM recoveries see the correct folder path but I still get the above error and I did manage to get this code as well:
I: using /data/media for sdcard/0/clockworkmod/ . last_install_path.
I: Cant partition non mmcblk device: /devices/platform/dw_mmc.2/mmc_host/mmc2
Click to expand...
Click to collapse
I have tried everything to try and get this to work as it should but I am stuck. Right now I have flashed the old Philz I have and restored a nandroid and the phone is fine. How do I get past these errors?
Any help would be greatly appreciated .
*edit*
I should mention that after the ICS flash I did a factory reset and wiped everything and still had the above errors...
Anyone?
CWM fails with a lot of roms. TWRP is better.
Hi, thanks for the input. Sadly TWRP also fails with the same error:
set_perm: some changes failed
E:Error in /data/media/0/ROM Install/wanamlite-v40-nb3.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
Hence the reason for my asking. Its not a bad zip so redownloading it will not get rid of the problem. My recoveries are also good zips otherwise they would not flash. Does anyone have any idea what is going on?
I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Sporty824 said:
I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not techy so don't know what exactly is going on, but I advise dealing with the mount problems before you proceed to flashing CM. If flashing stock again via RSD won't fix this, I assume your /data partition is faulty.
Sporty824 said:
I recently rooted my Droid Razr M XT907 and have had nothing but problems. Before rooting, I was on 4.4.2. I used the Towelroot app to root my phone, Root Checker to verify root, and Motopocalypse to unlock my bootloader. I tried to flash a custom recovery and I could not boot into recovery. I also tried to flash a new logo to get rid of the bootloader unlocked warning screen. Apparently I flashed a corrupted file because it caused my phone not to turn on right and I had to go straight to the boot menu and AP fastboot to flash stock 4.4.2 for my phone
. I then proceeded to root my phone again, and start over(except I didn't have to unlock my bootloader again). After another few hours, I finally got CWM Recovery v6.0.4.8 installed on my phone. I tried to wipe data/factory reset and it did this:
- - Wiping data. . .
Formatting /data. . .
Error mounting /data!
Skipping format. . .
Formatting /cache. . .
Formatting /sd-ext. . .
E: unkown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format. . .
Data wipe complete.
I am pretty sure that it did not format. I tried goint to mounts and storage menu and mounting /data there and it said:
Error mounting /data!
Thinking it was not a big deal, I proceeded to try and install zip from the external sd card. I went to Install Zip > Choose zip from /storage/sdcard1 and selected the zip I had on there called "cm- 11 -20140218-NIGHTLY-xt907.zip" and this is what it gave me:
- - Installing: /storage/sdcard1/cm- 11-20140218-NIGHTLY-xt907.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
This package is for "xt925, xt926, xt907, vanquish_u, vanquish, scorpion_mini, mb886, qinara, asanti, asanti_c, xt897, xt897c" devices; this is a " ".
E: Error in /storage/sdcard1/cm- 11 -20140218-NIGHTLY-xt907.xip
(Status 7)
Installation aborted
At this point, all i want to do is be able to flash Cyanogenmod on my phone. Is there any way to fix the mounting /data problem? Is there just an easier way to install Cyanogenmod at this point? Any help would be greatly appreciated.
Click to expand...
Click to collapse
First, you need to update your recovery. > http://goo.gl/7pDg47
Second, your trying to flash an outdated ROM that wont work on the updated KK bootloader. Go to the CM thread and download the correct version for your device. > http://goo.gl/Jx8EOu
Custom boot logos > http://goo.gl/fgOCNb
@ATTACK
Should I stick with CWM or switch to TWRP? Or is it just personal preference? Also, should I reflash stock and try again or just start reflashing the recovery and new ROM? The logo is lowest on my priority list btw.
Edit: So wait, is the Razr M XT907 a part of the Moto_MSM8960 devices? I could just install that like I would the other one?
Sporty824 said:
@ATTACK
Should I stick with CWM or switch to TWRP? Or is it just personal preference? Also, should I reflash stock and try again or just start reflashing the recovery and new ROM? The logo is lowest on my priority list btw.
Edit: So wait, is the Razr M XT907 a part of the Moto_MSM8960 devices? I could just install that like I would the other one?
Click to expand...
Click to collapse
Yup, it's personal preference. I prefer TWRP but just use whatever your comfortable with.
I see no need to go stock, just flash the new recovery then the ROM. And yes, all the moto_msm8960 devices have been unified, this includes the xt907. Just make sure you use the KK bootloader compatible version.
ATTACK said:
Yup, it's personal preference. I prefer TWRP but just use whatever your comfortable with.
I see no need to go stock, just flash the new recovery then the ROM. And yes, all the moto_msm8960 devices have been unified, this includes the xt907. Just make sure you use the KK bootloader compatible version.
Click to expand...
Click to collapse
OK. I downloaded a new custom recovery (I switched to TWRP since is was all touch based and I somehow broke the volume buttons on my last android). I then downloaded the newest CM and flashed it and the GAPPS. Everything works great. I even flashed a custom logo (the batman one). Thank you.
OK, someone please help, got everything else working, except data. I can't get mobile data working. I just want to know if there is anything I can do.
Sporty824 said:
OK, someone please help, got everything else working, except data. I can't get mobile data working. I just want to know if there is anything I can do.
Click to expand...
Click to collapse
Ummm.... try RSDing back to stock and see if your data comes back.
ATTACK said:
Ummm.... try RSDing back to stock and see if your data comes back.
Click to expand...
Click to collapse
Flashed back to stock. Still no data. Any other suggestions?
Edit: Nevermind, started working on stock after I flashed a new radio and reflashed stock. Going to try to install cm when I get home and hope it works
I reflashed stock, and data worked. I flashed CM11, and it didn't. I reflashed stock, and it worked again. I searched the problem online, again. I somehow found a site that I missed when I searched it the first few times. The site provided a fix that involved flashing cm11, gapps, and another zip. I tried it and it worked. For anyone who is having the same or similar problem, the link is below. Thank you ATTACK for all of the help and Deante Flood for making the zip that I flashed that made the data work again.
https://help.ting.com/entries/42358068-LTE-MMS-APN-Fix-Android-4-4-Kit-Kat-